DoiT International Outage History
21 incidents recorded over the last 365 days, 21 of them resolved. Durations are measured from when PulsAPI first saw the problem to when it cleared, which is usually longer than the vendor's own figure.
Every Recorded DoiT International Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| Oct 29, 2026 | AWS billing data delays in Cloud AnalyticsThis incident has been resolved. | 6h 19m | Resolved |
| Oct 26, 2026 | Inflated costs for Google Workspace, Microsoft 365, and LookerThe issue with inflated costs for Google Workspace, Microsoft 365, and Looker is resolved. Billing data and pro-forma invoices for October 2026 now show the correct amounts. Thank you for your patience. | 23h 21m | Resolved |
| Oct 5, 2026 | Degraded forecasting performance in Cloud AnalyticsThe Cloud Analytics forecasting issue has been resolved. All forecasting failures have been addressed, and forecasting, including forecast-dependent widgets and budgets, is operating normally. Thank you for your… | 18h 29m | Resolved |
| Sep 11, 2026 | Cost anomalies showing stale excess cost and statusThis incident has been resolved. | 57h 26m | Resolved |
| Sep 1, 2026 | Google Cloud issue [ONGOING]: Multiple Google Cloud servicesGoogle has resolved the incident and all components should be operational. | 25h 15m | Resolved |
| Jul 17, 2026 | AWS billing data issue causing inaccurate cost signals in DoiT Cloud IntelligenceThe AWS billing data issue has now been resolved. We have validated the recovery and confirmed that the affected cost data has stabilised. Related cost views and notifications in DoiT Cloud Intelligence should now… | 46h 48m | Resolved |
| Jun 26, 2026 | General issue with opening GCP Expert Inquiry tickets from the DCI ConsoleThe incident has been resolved. All systems are operating normally. | 37h 50m | Resolved |
| May 18, 2026 | Investigating incorrect April AWS cost data for some CloudHealth-managed customersCloudHealth’s fix has been validated on our side, and we have confirmed that the affected April AWS cost data has been corrected. At this time, the issue is resolved, and we are no longer seeing unexpected behavior… | 980h 6m | Resolved |
| May 8, 2026 | AWS missing dataWe are pleased to confirm that the AWS data ingestion issue in DoiT Cloud Intelligence, impacting consolidated resold customers, has now been resolved. All affected data ingestion workflows are operating normally… | 125h 16m | Resolved |
| Apr 6, 2026 | AWS missing dataWe have fully resolved the AWS data ingestion issues in DoiT Cloud Intelligence, including those impacting customers with AWS accounts managed via CloudHealth on shared payer accounts. Data is now populating as expected… | 96h 1m | Resolved |
| Mar 27, 2026 | Intermittent AWS ingestion issue affecting subset of DCI customersThe AWS ingestion issue in DoiT Cloud Intelligence has been resolved, and the affected data has been updated. Thank you for your patience. | 100h 19m | Resolved |
| Mar 26, 2026 | AWS missing dataWe have fixed the issue and expect data to be updated in your DCI console within the next few hours | 58 min | Resolved |
| Mar 6, 2026 | GCP Data Delivery Delays for billing exports to BigQueryGoogle has confirmed that the underlying issue causing delays in GCP Billing exports to BigQuery has been fixed, and data delivery has returned to normal. Our team has verified that recent billing data is being… | 63h 55m | Resolved |
| Feb 16, 2026 | Inaccurate AWS Cost DataThis incident has been resolved. | 269h 8m | Resolved |
| Feb 16, 2026 | Delayed GCP data delivery of cost and usage since February 11, 2026This incident has been resolved. | 70h 59m | Resolved |
| Jan 13, 2026 | Delayed GCP cost and usage data updates since January 10, 2026We have completed ingestion of the Google Cloud Platform (GCP) billing exports and are now seeing GCP cost and usage data fully up to date in the DoiT Console and Cloud Analytics. Our monitoring confirms that data… | 169h 27m | Resolved |
| Jan 3, 2026 | Subset of public APIs are unavailableThis incident has been resolved. Public APIs continue to operate normally and our monitoring has not detected any further issues. No additional customer impact is expected. | 7h 32m | Resolved |
| Dec 11, 2025 | Sign-in via Magic Link UnavailableThis incident has been resolved. | 4h 16m | Resolved |
| Dec 8, 2025 | Billing profiles unavailable in DoiT ConsoleAccess to Billing profiles in the DoiT console has been fully restored, and all services are operating as expected. We appreciate your understanding and thank you for your patience while our team worked to resolve this… | 44h 33m | Resolved |
| Dec 2, 2025 | Okta SSO sign-in issue impacting access to the DoiT consoleWe can confirm that service has been fully restored. Okta Single Sign-On (SSO) access to the DoiT Platform is now operating normally and sign-ins are completing as expected. Thank you for your patience and… | 19h 48m | Resolved |
| Nov 18, 2025 | DoiT Console: Degraded availability due to third‑party CDNWe can confirm that the issue with the third-party content delivery network has been fully resolved. Console access and performance have returned to normal. We appreciate your patience and understanding. | 19h 32m | Resolved |
Hear about the next one while it is open
Everything above is a record written after the fact. We can email you when the next DoiT International incident opens instead, at the point where knowing still changes what you do.
Free, no password, no card. Unsubscribe in one click.
How to Read This DoiT International Incident Log
Each row is an incident PulsAPI observed, not a summary written afterwards. The duration is wall-clock time between the first failing check and the first clean one, so it includes the window before DoiT International acknowledged anything. Vendor post-mortems typically measure from acknowledgement, which is why their numbers are usually shorter.
Incidents still open have no duration yet and are listed as ongoing rather than being given a running total. The archive covers the last 365 days; anything older has aged out of the window rather than never having happened.
The longest single DoiT International outage in this window ran 40d 20h, against a mean recovery of 4d 8h. If you depend on DoiT International in a customer-facing path, the longest figure is the one to design around. The mean is what happens on a normal bad day; the maximum is what happens on the worst one.