Vendor reports: degradedResolved · vendor status “resolved”Official status API

Unable to open manage portal and StatusPage intermittently

Reported by Statuspage · Observability & Incident · source last read just now

Official source (opens in a new tab)
Vendor start
Apr 9, 2026, 07:10 UTC
Vendor's clock
Resolved
Apr 9, 2026, 07:38 UTC
Vendor's clock
First seen by Statuswall
Before tracking began
Statuswall's clock
Duration
29 min
From vendor start and resolution

Summary

Built from the facts below, no AI

Potential impact, not a confirmed outage of your systems.

What the vendor confirmed

  • Statuspage reports degraded: "Unable to open manage portal and StatusPage intermittently".[E1, E2]
  • The vendor marked it resolved at 2026-04-09 07:38 UTC.[E3, E7]

Affected products and regions

  • Components: HTTP Pages, Admin User+Pass, Web Portal, Statuspage, Pingdom Email, Email, Pingdom Integration, Ticketing, HTTPS Pages, Admin Google Auth, Authenticated API, External, New Relic Email, Slack, SMS, Knowledge Base, Status Embed Widget, Admin SAML 2.0, DNS Validation, Generic Email, Webhook, New Relic Integration, API Documentation, SSL Provisioning, Public API, Page Access Users, PagerDuty Webhook, Twitter, Datadog Integration, Metastatuspage, Page Google Auth, Billing, Custom Integration, Shortlinks, Jira Software Integration, Marketing Site (www.statuspage.io), Page SAML 2.0, SMS Subscription, Page IP Restriction, Signup, AWS cloudfront, AWS rds-us-west-2, AWS route53.[E6]

What is unknown

  • Which regions are affected: the vendor did not say.[E5]
  • Whether your own systems are affected: a vendor report cannot tell you; check your monitoring.

Last update in these facts: 2026-04-09 07:38 UTC · summary s1, evidence 2694d14e50ceea54

Evidence (7)
  1. E1Statuspage reports degraded. (vendor) source (opens in a new tab)
  2. E2Vendor title: "Unable to open manage portal and StatusPage intermittently". (vendor) source (opens in a new tab)
  3. E3Vendor status word: "resolved". (vendor) source (opens in a new tab)
  4. E4Vendor-reported start: 2026-04-09 07:10 UTC. (vendor) source (opens in a new tab)
  5. E5The vendor did not state which regions are affected. (Statuswall)
  6. E6Components the vendor attached: HTTP Pages, Admin User+Pass, Web Portal, Statuspage, Pingdom Email, Email, Pingdom Integration, Ticketing, HTTPS Pages, Admin Google Auth, Authenticated API, External, New Relic Email, Slack, SMS, Knowledge Base, Status Embed Widget, Admin SAML 2.0, DNS Validation, Generic Email, Webhook, New Relic Integration, API Documentation, SSL Provisioning, Public API, Page Access Users, PagerDuty Webhook, Twitter, Datadog Integration, Metastatuspage, Page Google Auth, Billing, Custom Integration, Shortlinks, Jira Software Integration, Marketing Site (www.statuspage.io), Page SAML 2.0, SMS Subscription, Page IP Restriction, Signup, AWS cloudfront, AWS rds-us-west-2, AWS route53. (vendor) source (opens in a new tab)
  7. E7Vendor-reported resolution: 2026-04-09 07:38 UTC. (vendor) source (opens in a new tab)

Affected scope

Not stated by the vendor

Components: HTTP Pages, Admin User+Pass, Web Portal, Statuspage, Pingdom Email, Email, Pingdom Integration, Ticketing, HTTPS Pages, Admin Google Auth, Authenticated API, External, New Relic Email, Slack, SMS, Knowledge Base, Status Embed Widget, Admin SAML 2.0, DNS Validation, Generic Email, Webhook, New Relic Integration, API Documentation, SSL Provisioning, Public API, Page Access Users, PagerDuty Webhook, Twitter, Datadog Integration, Metastatuspage, Page Google Auth, Billing, Custom Integration, Shortlinks, Jira Software Integration, Marketing Site (www.statuspage.io), Page SAML 2.0, SMS Subscription, Page IP Restriction, Signup, AWS cloudfront, AWS rds-us-west-2, AWS route53

No region Statuswall recognises is stated for this incident (place names and provider-specific codes are not converted). It is not assumed to be global.

Potential relevance

Statuspage is not in your stack. Follow it to see whether reports like this fall inside the regions you use.

Timeline

Vendor times come from the vendor. “Seen by Statuswall” times are when Statuswall noticed a change, which can lag the vendor by a few minutes. Statuswall does not store the vendor's update text; read it on the official page.

  1. Apr 9, 2026, 07:10 UTCVendor-reported startVendor time
  2. Apr 9, 2026, 07:38 UTCVendor-reported resolutionVendor time

No changes observed yet. Statuswall began recording changes on incidents in November 2026.