GitHub: Delayed Actions status check results
What happened?
We are investigating reports of degraded performance for Actions
GitHub, OpenAI, Cloudflare, AWS and the other services your product runs on: what is down, when it started and how long it lasted. Check here before you debug your own stack.
Active incident
Our team is currently investigating a connectivity issue in our Dallas data center. This is strictly affecting traffic routed via IPv6 to Google and its associated products, which may cause intermittent connection timeouts. We will post further updates as soon as more information becomes available.
View incident →Click any outage to explore the incident.
We are investigating reports of degraded performance for Actions
Users are experiencing issues accessing Notion, including signing in and loading pages. Some users may see a blocked-access message or pages stuck loading. We are investigating and working to restore access.
Our helpdesk provider is currently experiencing issues, and as such customers might encounter errors while submitting or viewing tickets. Responses on customer inquiries may be delayed during this time.
There’s a Salesforce service disruption. During a service disruption, end users can’t access the service. We’re investigating the issue and an update will be provided in 30 minutes or sooner if we have more information.
The other half
This page tells you what is down across the internet right now. It cannot tell you whether your own site is experiencing an incident, and that is the part your users notice. UptimeRobot checks your websites, APIs and servers, and tells you when one of them does.
Create a free account50 monitors free. No card.
The issue has been identified and mitigation is in process.
Akamai is aware of the recently published F5/NGINX vulnerabilities (CVE-2026-15176, CVE-2026-97205, and CVE-2026-93479), and our teams are investigating their potential impact across our platform and infrastructure.F5 has released out-of-band security patches addressing three critical severity vulnerabilities in NGINX Open Source and NGINX Plus. These vulnerabilities may allow unauthenticated attackers to trigger heap buffer overflows, which could cause a denial of service or potential remote code execution if ASLR is bypassed.If you are running a vulnerable version of NGINX Open Source or NGINX Plus, we recommend following guidance from F5/NGINX and applying available patches.We will post more details for customers and partners with a valid Control Center login at https://community.akamai.com/customers/s/group/0F90f000000DFgx/service-incident-notifications as additional information becomes available. If you have questions or are experiencing an impact due to this issue, please use the Support Center on Akamai Community, or Akamai Control Center, to contact Akamai Technical Support. Contact information is available at https://www.akamai.com/us/en/support/.
Akamai is aware of the recently published F5/NGINX vulnerabilities (CVE-2026-15176, CVE-2026-97205, and CVE-2026-93479), and our teams are actively investigating their potential impact across our platform and infrastructure. F5 has released out-of-band security patches addressing three critical severity vulnerabilities in NGINX Open Source and NGINX Plus. These vulnerabilities may allow unauthenticated attackers to trigger heap buffer overflows, which could cause a denial of service or potential remote code execution if ASLR is bypassed. If you are running a vulnerable version of NGINX Open Source or NGINX Plus on a Linode instance, we recommend following guidance from F5/NGINX and applying available patches. We will provide updates as additional information becomes available.
Since 20:19 UTC, new Network Error Logging (NEL) reports are not being processed. Reports received during this period will not appear in Network Error Logging analytics. Website traffic and other services are not affected. We are investigating and will provide an update as soon as possible.
Edge Functions and Function logs from the period between 13:58–15:35 UTC may be delayed in appearing in the Netlify UI and in log drains. We are working to process the backlog; function and edge function requests are not affected.
We're currently investigating a Partial Service disruption of the Bancontact payment method that began at 14:08 UTC. This issue is external to Stripe and is causing increased error rates for transactions processed through the Bancontact payment method. We are actively monitoring the situation and will provide updates as more information becomes available.
We are investigating reports of degraded performance for Actions
We have not identified customer impact related to the PHP vulnerabilities reported on October 21, 2026. Our security and engineering teams are reviewing potential exposure in NodeJS services and across Zapier. The assessment is ongoing. We will share further findings here as they are confirmed. Please reach out to our Support team "Support team": https://zapier.com/app/get-help if you need any help in the meantime.
We are investigating elevated error rates and increased response times on the Management API across multiple regions. Some operations that depend on it, such as creating new projects, may fail or be slow.
We are investigating an issue with inbound RCS events. Users may experience elevated HTTP 500 and 503 status codes when receiving inbound RCS events. We will provide another update in 1 hour or as soon as more information becomes available.
We are investigating elevated errors affecting connectors. We will provide an update as soon as possible.
The Notion MCP query_data_source tool is temporarily unavailable in Claude clients.
We are currently investigating this issue.
This is impacting users in India, Japan, and Korea. We are investigating the issue for the listed services.
HubSpot is aware of the recently disclosed PHP security vulnerability. PHP isn't part of HubSpot's infrastructure, and we are not aware of any impact to our platform or customers. We will continue to watch the situation and provide an update if our assessment changes.
We are investigating elevated errors on requests to Claude Fable 5. We will provide an update as soon as possible.
Where our outage data comes from, and how we treat it.
We watch the status pages of the major providers around the clock, so you do not have to check twenty of them.
Every entry comes from an incident reported for that provider. No guess work at play.
Each entry names the provider and the time it was reported, in UTC, so you can check it against their own status page.
Some providers never close an incident. We stop showing an incident as ongoing after 3 days rather than let it run forever.
There's nothing to install. No credit card required. 50 monitors for free.