OutageDB

No impact incident

BAS: This is an example incident

Oct 2, 2026, 15:05 UTC
started
15:21 UTC
resolved October 1, 2026
—
duration

Current status of BAS: Operational — live BAS status

Timeline

  1. Oct 1, 2026, 15:11 UTC
    monitoring
    Let your users know once a fix is in place, and keep communication clear and precise.
  2. Oct 1, 2026, 15:17 UTC
    identified
    As you continue to work through the incident, update your customers frequently.
  3. Oct 1, 2026, 15:21 UTC
    resolved
    Empathize with those affected and let them know everything is operating as normal.
  4. Oct 1, 2026, 15:47 UTC
    investigating
    When your product or service isn’t functioning as expected, let your customers know by creating an incident. Communicate early, even if you don’t know exactly what’s going on.

Updates as published by BAS (original).

Other services with incidents at the same time