Is GitHub Webhooks down? Check the current status
GitHub Webhooks is operational
Updated
GitHub Webhooks is operational
Updated
Join companies like Adobe, Coursera, and Glassdoor that use IsDown to monitor their vendors.
IsDown pulls data from GitHub's status page every few minutes and collects user-reported issues. Refresh the page to see if there are any updates.
This chart displays the number of user-reported issues over the past 24 hours, grouped into 20-minute intervals. It's normal to see occasional reports, which may be due to individual user issues rather than a broader problem. We only consider an issue widespread if there are multiple reports within a short timeframe.
No comments yet
IsDown has tracked 44 incidents for GitHub Webhooks since started monitoring GitHub status in April 2020.
29 days ago · lasted about 1 hour
We are investigating reports of degraded performance for Pages More details
about 2 months ago · lasted about 1 hour
We are investigating reports of degraded performance for API Requests, Git Operations and Issues More details
2 months ago · lasted 37 minutes
We are investigating reports of degraded performance for Actions, Codespaces, Git Operations, Issues and Webhooks More details
We've tracked and collected 44 incidents for GitHub Webhooks since started monitoring GitHub status
Webhooks is part of GitHub. Check the GitHub's status.
5 incidents in 2025
Number of Incidents
1 issues
Last incident
30 days ago
AWS
Google Cloud
Google Workspace
Azure
Cloudflare
Slack
Zoom
Datadog US1
Figma
Adobe
HubSpot
Microsoft 365
Aircall
Stripe
Airtable
Why teams choose IsDown:
14-day free trial • No credit card required
Get instant alerts when your cloud vendors experience downtime. Create an internal status page to keep your team in the loop and minimize the impact of service disruptions.
You can check the GitHub Webhooks status page on IsDown to see if there are any ongoing issues affecting webhook deliveries. Additionally, you can visit the official GitHub status page to confirm if there are any reported disruptions. If your webhooks are failing, inspect your repository webhook settings and review the recent deliveries section.
If your webhook deliveries are delayed or missing, check if GitHub is experiencing an outage. You can also verify that a webhook delivery was sent correctly by reviewing the payload and inspecting logs in the GitHub Webhooks status page.
If there is a widespread issue with webhook events and payloads, it will be reflected on the GitHub Webhooks status page. You can also check the REST API endpoints for repository webhooks to inspect individual event failures.
If you suspect a webhook-related outage, you can perform validating webhook deliveries by checking headers, timestamps, and response codes. If webhooks are failing due to a GitHub service issue, monitor the status page for updates.
If your repository webhook that is subscribed is not triggering, confirm that GitHub is sending requests to the correct URL. You can also use the REST API endpoints for repository webhooks to troubleshoot webhook failures.
Yes, testing webhooks manually can help diagnose issues during service disruptions. You can create a new webhook and use a local server to capture events. If GitHub is experiencing an issue, use the status page to track updates.
Currently there's no report of GitHub Webhooks being slow. Check on the top of the page if there are any reported problems by other users.
IsDown monitors the GitHub Webhooks official status page every few minutes. We also get reports from users like you. If there are enough reports about an outage, we'll show it on the top of the page.
GitHub Webhooks last outage was on March 20, 2025 with the title "Incident with Pages"
IsDown and DownDetector help users determine if a service is having problems. The big difference is that IsDown is a status page aggregator. IsDown monitors a service's official status page to give our customers a more reliable source of information. The integration allows us to provide more details about the outage, like incident title, description, updates, and the parts of the affected service. Additionally, users can create internal status pages and set up notifications for all their third-party services.
IsDown offers an easy way to monitor GitHub with maximum flexibility
IsDown monitors Webhooks for major outages. A major outage is when Webhooks experiences a critical issue that severely affects one or more services/regions. When GitHub marks an incident as a major outage, IsDown updates its internal status, the customer status page and dashboard. Depending on the customer settings, IsDown will also send notifications.
IsDown monitors GitHub status page for minor outages. A minor outage is when Webhooks experiences a small issue affecting a small percentage of its customer's applications. An example is the performance degradation of an application. When a minor outage occurs, IsDown updates its internal status and shares that information on the customer status page. Depending on the customer settings, IsDown will also send notifications.
IsDown collects all information from the outages published in GitHub status page to provide the most accurate information. If available, we gather the title, description, time of the outage, status, and outage updates. Another important piece of information is the affected services/regions which we use to filter the notifications that impact your business.
GitHub publishes scheduled maintenance events on their status page. IsDown collects all the information for each event and creates a feed that people can follow to ensure they are not surprised by unexpected downtime or problems. We also send the feed in our weekly report, alerting the next maintenances that will take place.
IsDown monitors GitHub and all their 11 components that can be affected by an outage. IsDown allows you to filter the notifications and status page alerts based on the components you care about. For example, you can choose which components or regions affect your business and filter out all other outages. This way you avoid alert fatigue in your team.
GitHub and other vendors don’t always report outages on time. Our crowdsourced status platform helps you stay ahead of outages. Users report issues and outages, sharing details on what problems they are facing. We use that info to provide early signs of outages. This way, even without an official update, you can stay ahead of possible problems.
14-day free trial · No credit card required · No code required
