Is Aviator down?
Last checked just nowNo incidents right now.
Aviator is operational right now. Last checked just now; the most recent incident resolved 19h ago.
Real-time Aviator status, recent outages, and incident history: pulled directly from Aviator's official status page at status.aviator.co every 5 minutes. Pingoru tracks 6 Aviator services and has captured 3 incidents in the last 90 days (98.89% uptime). Get email, Slack, Discord, or webhook alerts the moment Aviator reports a new incident, free for 3 monitors, no credit card.
Recent outages & incidents
Past 90 days- Background queuesManagement dashboard
Timeline · 4 updates
- identified · Oct 27, 2026, 01:35 AM UTC
We have identified and issue, triggering rollback
- identified · Oct 27, 2026, 01:36 AM UTC
We are continuing to work on a fix for this issue.
- monitoring · Oct 27, 2026, 01:45 AM UTC
Rollback is complete, things are back to normal, monitoring the status
- resolved · Oct 27, 2026, 02:02 AM UTC
All services are working. If you enqueued a PR between 6.27-6.45pm PDT, you may have to requeue it.
Latest: All services are working. If you enqueued a PR between 6.27-6.45pm PDT, you may have to requeue it.
-
- Background queues
Timeline · 6 updates
- investigating · Aug 11, 2026, 08:43 PM UTC
We are currently investigating a backed up queue. This could also cause delay in action for queueing or dequeueing a PR
- investigating · Aug 11, 2026, 08:43 PM UTC
We are continuing to investigate this issue.
- investigating · Aug 11, 2026, 09:16 PM UTC
We are continuing to investigate this issue.
- investigating · Aug 11, 2026, 09:27 PM UTC
We've deployed an initial fix, we're monitoring currently.
- monitoring · Aug 11, 2026, 09:33 PM UTC
The queue should be operational again, we're continuing to actively monitor the situation.
- resolved · Aug 11, 2026, 09:49 PM UTC
The incident is resolved. Root cause: A large bulk team-reorganization in one customer's GitHub organization triggered database lock contention in our team-sync handler, which consumed the shared worker pool that processes all the background tasks.
Latest: The incident is resolved. Root cause: A large bulk team-reorganization in one customer's GitHub organization triggered database lock contention in our team-sync handler, which cons…
-
Incident record
Since April 2026 · Statuspage by Atlassian · 6 components checked every 5 minutesThe longest incident in the last year, Web app requests and APIs are degraded on July 14, 2026, ran for 8 hours. 3 maintenance windows announced in the same period.
Most affected components, last 12 months
- Background queues2
- Management dashboard2
Latest incidents
- Web dashboard and backend is unavailable
We have identified and issue, triggering rollback
- Queue backed up
We are currently investigating a backed up queue. This could also cause delay in action for queueing or dequeueing a PR
- Web app requests and APIs are degraded
Queues are working properly however the dashboard and APIs are degraded. Investigating.
- Started Oct 27, 2026, 01:30 AM UTC · Resolved Oct 27, 2026, 02:02 AM UTC · 32m
- Queue backed up ResolvedStarted Aug 11, 2026, 08:43 PM UTC · Resolved Aug 11, 2026, 09:49 PM UTC · 1h 6m