Radar had 13 outages in the last 2 years totaling 30h 39m of downtime — averaging 0.5 incidents per month.
There were 13 Radar outages since July 30, 2024 totaling 30h 39m of downtime. Each is summarised below — incident details, duration, and resolution information.
We're experiencing an elevated level of API latencies and are currently looking into the issue.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are currently investigating this issue.
This incident has been resolved.
Since 20:00 UTC downstream webhook calls that use Radar static IPs are delivering more slowly. The queue that delivers those calls is backed up. On-call engineers have added additional capacity and are continuing to increase capacity.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We're experiencing an elevated level of API errors. The issue is related to a Cloudflare incident (https://www.cloudflarestatus.com/incidents/dz87vqwvl8wr).
Cloudflare has implemented a fix and is monitoring the results.
All services are operating normally. We are continuing to monitor for any further issues.
This incident has been resolved.
Reporting performance is degraded. This incident is related to an ongoing AWS service disruption and an earlier incident (https://status.radar.com/incidents/2w04wqy39ylw). We are investigating.
Reports are loading intermittently, but performance is still degraded.
Dashboard and reporting performance continues to be degraded. This incident is related to an ongoing AWS service disruption.
Dashboard and reporting performance continues to be degraded. Data on some pages and reports is delayed, but catching up.
Dashboard and reporting performance are now operational. Data on some pages and reports is delayed, but catching up.
This incident has been resolved.
Between 08:24 and 09:34 UTC, integrations and webhooks were impacted by a major outage. Additionally, between 08:49 and 10:19 UTC, our dashboard was impacted by a major outage. APIs remained fully operational during this time. While integrations and most of the dashboard are operational, reporting performance may still be degraded. This incident was caused by an AWS service disruption, which has since been mitigated and is now recovering (https://health.aws.amazon.com/health/status?eventID=arn:aws:health:us-east-1::event/MULTIPLE_SERVICES/AWS_MULTIPLE_SERVICES_OPERATIONAL_ISSUE/AWS_MULTIPLE_SERVICES_OPERATIONAL_ISSUE_BA540_514A652BE1A).
The Locations page in the dashboard is loading slowly or timing out. However, the track API is operating normally. We are investigating the issue.
The Usage and Analytics pages in the dashboard are also loading slowly or timing out. We are continuing to investigate the issue.
An AWS Athena service issue is impacting the queries that power the Locations, Usage, and Analytics pages. We are waiting for updates from AWS support.
AWS support has informed us that they are continuing to work on a fix for this issue.
This incident appears to be resolved, but we are waiting for confirmation from AWS support.
This incident has been resolved.
A code change that was deployed on April 24th evening ET resulted in map tiles not loading when using the default Radar map style and older MapLibre versions (3.x or earlier). This change is actively being reverted by the Radar engineering team.
The fix is deploying to the production fleet.
This incident has been resolved.
We're experiencing an elevated level of API latencies and are currently looking into the issue.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We're experiencing an elevated level of API errors and are currently looking into the issue.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
We are continuing to monitor for any further issues.
This incident has been resolved.
We are currently investigating this issue.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
Latency is elevated for some web SDK track requests. The issue has been identified and a fix is being implemented.
This incident has been resolved.
We're experiencing an elevated level of errors for maps and are currently looking into the issue.
The issue has been identified and a fix is being implemented.
This incident has been resolved.