Athena Outage History

Athena is up right now

Pingoru has recorded 5 incidents for Athena: 5 in the last 12 months and 4 in the last 90 days.

Source: status.athenaag.com

5incidents recorded
5last 12 months
4last 90 days
4 hourstypical duration

Incidents, newest first

Critical October 2, 2026 Vendor-reported: Cloudflare Edge Delivery (Cloudflare) 15m Cloudflare Edge Delivery

Started Oct 02, 2026, 09:50 PM UTC· resolved Oct 02, 2026, 10:05 PM UTC

  1. monitoring Oct 02, 2026, 09:50 PM UTC

    Cloudflare reports a service incident affecting a dependency of Cloudflare Edge Delivery. This is a vendor-reported notice; the extent of impact to individual Athena users is not yet confirmed. Vendor status: https://www.cloudflarestatus.com/incidents/2xnmsnv8yv5x

  2. resolved Oct 02, 2026, 10:05 PM UTC

    Cloudflare reports recovery. The vendor incident is resolved and its mapped service components were healthy on two checks at least four minutes apart. This confirms vendor-reported recovery; it does not test every Athena workflow. Vendor status: https://www.cloudflarestatus.com/incidents/2xnmsnv8yv5x

Read the full incident report →

Minor September 29, 2026 Vendor-reported: ChatGPT Enterprise (OpenAI) 18h 48m ChatGPT Enterprise

Started Sep 29, 2026, 06:41 PM UTC· resolved Sep 30, 2026, 01:29 PM UTC

  1. investigating Sep 29, 2026, 06:41 PM UTC

    OpenAI reports a service incident affecting a dependency of ChatGPT Enterprise. This is a vendor-reported notice; the extent of impact to individual Athena users is not yet confirmed. Vendor status: https://status.openai.com/incidents/01M3Q4RK1SM4EMK445GGPG7C0N

  2. monitoring Sep 29, 2026, 07:45 PM UTC

    OpenAI reports a service incident affecting a dependency of ChatGPT Enterprise. This is a vendor-reported notice; the extent of impact to individual Athena users is not yet confirmed. Vendor status: https://status.openai.com/incidents/01M3Q4RK1SM4EMK445GGPG7C0N

  3. identified Sep 30, 2026, 05:50 AM UTC

    OpenAI reports a service incident affecting a dependency of ChatGPT Enterprise. This is a vendor-reported notice; the extent of impact to individual Athena users is not yet confirmed. Vendor status: https://status.openai.com/incidents/01M3RDNY37CAPQGRKPBVMNRT4K

  4. monitoring Sep 30, 2026, 06:05 AM UTC

    OpenAI reports a service incident affecting a dependency of ChatGPT Enterprise. This is a vendor-reported notice; the extent of impact to individual Athena users is not yet confirmed. Vendor status: https://status.openai.com/incidents/01M3RDNY37CAPQGRKPBVMNRT4K

  5. resolved Sep 30, 2026, 01:29 PM UTC

    Correction: A later OpenAI incident limited to ChatGPT Pro and Plus users was incorrectly linked to this ChatGPT Enterprise notice. OpenAI resolved the earlier broadly scoped ChatGPT incident, and its mapped ChatGPT functions now report operational. We are resolving this vendor-reported notice and reviewing the mapping before automatic OpenAI updates resume. If you still experience an issue, contact Athena support.

Read the full incident report →

Notice September 12, 2026 Brief status-graph gap for location reliability 10m

Started Sep 12, 2026, 01:50 PM UTC· resolved Sep 12, 2026, 02:00 PM UTC

  1. resolved Sep 12, 2026, 02:00 PM UTC

    Around 9:50 AM Eastern on September 12, our location-reliability graph dropped to zero for about 10 minutes because the monitor briefly lost contact with the network controller. We do not have evidence that both offices lost internet. The graph returned to normal by 10:00 AM. If you had a real connection problem this morning, please tell IT.

Read the full incident report →

Notice September 11, 2026 Brief network interruption at Sacramento 10m

Started Sep 11, 2026, 09:20 PM UTC· resolved Sep 11, 2026, 09:30 PM UTC

  1. resolved Sep 11, 2026, 09:00 PM UTC

    Around 5:20 PM Eastern on September 11, many network devices at our Sacramento location briefly went offline. Site internet at the main gateway stayed up. Everything we monitor came back within about 10 minutes. If you still had trouble connecting after 5:30 PM, please tell IT.

Read the full incident report →

Notice April 23, 2026 This is an example incident 10m

Started Apr 23, 2026, 04:48 PM UTC· resolved Apr 23, 2026, 04:58 PM UTC

  1. monitoring Apr 23, 2026, 04:48 PM UTC

    Let your users know once a fix is in place, and keep communication clear and precise.

  2. identified Apr 23, 2026, 04:54 PM UTC

    As you continue to work through the incident, update your customers frequently.

  3. resolved Apr 23, 2026, 04:58 PM UTC

    Empathize with those affected and let them know everything is operating as normal.

  4. investigating Apr 23, 2026, 05:24 PM UTC

    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.

Read the full incident report →