New AI Incident Response, Multi-Region Agents, and Custom-Domain Status Pages, May 2026
Monitor Features overview Vendor status Uptime & synthetic checks Certificate lifecycle Operate Incident management Live demo
By goal Replace your stack Why ServiceAlert Competitor comparisons Alternatives directory By signal Reliability hub   · Uptime rankings   · SLA compliance Outage map
Services
Check & scan SSL security grader Status checker DNS lookup Response time WHOIS lookup Calculators SLA calculator Downtime calculator Embed Status badges All tools →
Pricing
Guides Help center Uptime monitoring RUM & analytics Teams & shared monitors Developer API reference Status badges Learn Blog Outage reports FAQ Changelog
Dashboard

DoiT International Outage History

Uptime record, past incidents, and downtime history for DoiT International.

Checking current status...
44% uptime over 91 days
99.9% ✗ 99.5% ✗ 99% ✗ 95% ✗

90-Day Trend

Mar 30Jun 27

Monthly Uptime

Month Uptime Days Tracked Days with Issues
June 2026 0% 27 27
May 2026 45.2% 31 17
April 2026 86.7% 30 4
March 2026 0% 3 3

Uptime is calculated from daily worst-status snapshots. A day with any non-operational status counts as a day with issues.

Daily Status (Last 91 Days)

Mar 29 Today
Operational Degraded Partial Outage Major Outage Maintenance No Data

Incident History

June 2026
General issue with opening GCP Expert Inquiry tickets from the DCI Console
minor

Started: Jun 26, 11:12 PM

identified
The issue has been identified, and a fix is being implemented.
Jun 27, 11:05 AM
investigating
We are currently investigating an issue impacting Google Cloud ticket submissions in the DCI Console. When attempting to open a ticket, the required GCP Project field displays no available options, preventing successful submission. If you are blocked by this issue and need to submit an urgent request, please select DoiT Console as the Cloud Platform and provide the full details of your request in the body of the ticket.
Jun 26, 11:12 PM
May 2026
Investigating incorrect April AWS cost data for some CloudHealth-managed customers
minor

Started: May 18, 1:05 PM

monitoring
CloudHealth has advised that they have implemented a fix for this issue and updated the affected data. We are now monitoring the data to ensure everything continues to behave as expected. We appreciate your continued patience while we complete these checks.
May 27, 1:47 PM
identified
CloudHealth has advised that they have implemented a fix for this issue, and we are now monitoring and validating the outcome on our side. At this time, we are reviewing the data on our side to verify its integrity. We will share a further update once this validation is complete. Thank you for your patience and understanding.
May 26, 6:46 AM
identified
CloudHealth has identified the affected customers and is currently updating their billing data. We are continuing to closely monitor their progress. Once CloudHealth confirms the data update is complete, we will review the results on our side and share a further update. Thank you for your patience and understanding.
May 20, 9:14 AM
investigating
We are investigating a recurrence of a CloudHealth-related issue affecting April AWS cost data and assessing the impact on April invoices for multiple customers. Some customers may see inaccurate or otherwise inflated April charges in DoiT Cloud Intelligence. Our current checks indicate that the values shown in DoiT match the data currently available in CloudHealth, and we are working with CloudHealth to confirm scope and resolution steps. We will share another update as soon as we have more ...
May 18, 1:05 PM
AWS missing data

Started: May 8, 11:49 AM

monitoring
The issue has been identified, and a fix is being implemented.
May 10, 6:35 AM
investigating
We have identified an AWS data ingestion issue in DoiT Cloud Intelligence impacting consolidated resold customers, we will provide an update shortly
May 8, 11:49 AM
April 2026
AWS missing data
minor

Started: Apr 6, 1:39 PM

monitoring
We are continuing to monitor AWS data ingestion in DoiT Cloud Intelligence. We have observed a recurrence of ingestion issues affecting a subset of customers. Customers whose AWS accounts are managed via CloudHealth on shared payer accounts may experience delayed or incomplete AWS cost data due to an upstream issue in CloudHealth. Data for other customers remains up to date, and we are closely monitoring all ingestion pipelines and working with CloudHealth to restore normal operation.
Apr 8, 11:14 AM
monitoring
We have implemented a fix for the AWS ingestion problem in DoiT Cloud Intelligence. The data for affected customers has been updated, and we are actively monitoring the ingestion pipeline to ensure stability.
Apr 7, 12:07 PM
identified
We have identified an issue affecting AWS customers regarding missing data
Apr 6, 1:39 PM
March 2026
Intermittent AWS ingestion issue affecting subset of DCI customers
minor

Started: Mar 27, 12:02 PM

monitoring
The AWS data ingestion is currently working as expected. Our Engineering Team is continuing to monitor to ensure the issue is fully resolved. We will update further as the resolution is fully confirmed.
Mar 30, 2:53 AM
monitoring
We have deployed a fix to address the AWS ingestion issue in DCI. The impacted customers’ data has now been updated, and we are closely monitoring the ingestion pipeline to ensure it remains stable and no further impact occurs.
Mar 27, 4:09 PM
identified
We have identified a problem with AWS data ingestion. Some customers are facing issues with AWS cost and usage data in DoiT Cloud Intelligence, while others are unaffected. Impacted tenants are experiencing delayed or missing AWS data in analytics and dashboards. We are actively working to identify the scope of the issue and are developing remediation steps simultaneously. Thank you for your understanding during this time.
Mar 27, 12:02 PM
View live status for DoiT International Browse all services