Is GitHub Webhooks Down?

This page shows the live GitHub Webhooks status so you can confirm in seconds if GitHub Webhooks is down.

GitHub Webhooks current status

Updated

GitHub Webhooks is operational

IsDown pulls data from the official status page every few minutes and collects user-reported GitHub Webhooks issues.
Refresh the page to see the latest updates.

GitHub Webhooks user-reported issues in the last 24 hours

This chart displays the number of user-reported GitHub Webhooks problems 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.

IsDown Logo Third-party monitoring

Stop Juggling Dozens of Status Pages – Monitor Them All in One Place

Monitoring 4000+ third-party services in real-time
Get custom alerts via Slack, Teams, Datadog, etc.
Create public or private status pages
Start Free Trial
14-day free trial · No credit card required
Trusted by thousands of teams

GitHub Webhooks outage history

IsDown has tracked 44 incidents for GitHub Webhooks since started monitoring GitHub downtimes in April 2020. We are also collecting data from 4000+ services, and normalize the data to give you a clear picture of the impact of the outage.

  • Mar 20 2025

    about 2 months ago · lasted about 1 hour

    We are investigating reports of degraded performance for Pages

  • Mar 03 2025

    2 months ago · lasted about 1 hour

    We are investigating reports of degraded performance for API Requests, Git Operations and Issues

  • Feb 16 2025

    3 months ago · lasted 37 minutes

    We are investigating reports of degraded performance for Actions, Codespaces, Git Operations, Issues and Webhooks

  • Jan 09 2025

    4 months ago · lasted about 1 hour

    We are investigating reports of degraded availability for Webhooks

  • Jan 07 2025

    4 months ago · lasted about 2 hours

    We are investigating reports of degraded performance for Actions

  • Apr 2020 ...
    IsDown started monitoring GitHub status

    We've tracked and collected 44 incidents for GitHub Webhooks since started monitoring GitHub status

Sign up and check all outage history

Latest user comments about GitHub Webhooks issues

No comments yet

GitHub Webhooks outages in the last 30 days

Number of Incidents

0 issues

Last incident

50 days ago

IsDown Logo Seamless Integrations

Get GitHub outage alerts and updates in your favorite tools

Receive vendor outage notifications where your team already works. Compatible with Slack, Microsoft Teams, PagerDuty, Datadog, Better Stack, Rootly, Incident.io, Statuspage.io, and more.
Never miss an outage
Easy setup · No coding required
Works with your existing stack

Having problems with GitHub Webhooks? What can you do?

  1. First, stay calm.

    • We know it's stressful when GitHub Webhooks is down, but running around is not going to fix it.
    • Remember that it's normal for services to go down sometimes. It can be for a number of reasons, from maintenance to unexpected issues.
  2. Make a quick evaluation of the impact of the GitHub Webhooks outage

    • Try to evaluate the impact of the outage on your business. Is it impacting a majority of your users or just a few?
    • Did GitHub Webhooks already acknowledge the issue? And published a status update? (You can find it in the top of the page or in GitHub Webhooks status page)
    • If not, understand if other users are also experiencing issues. You can also check this information on the top of the page.
  3. Communicate with your team and users quickly

    • If GitHub Webhooks is having problems and impacting your business, it's important to keep your team and users informed.
    • Share this page with your team, so you can start incident response procedures. No need for everyone to go around searching for information. Create a post or a specific channel in your internal communication tools (Slack, Teams, Google Chat, etc.) so you can aggregate all the information in one place.
    • If you have a status page, create a status update to inform your users about the issue. This way they know what's going on and you can avoid a flow of support requests overburding your team.
  4. Understand the root cause

    • After the first communication, let's move on to the next step. Do a more thorough investigation to understand the root cause of the issue and impact.
    • Reach out to the service provider to understand if they are aware of the issue and if they are already working on it. You can reach them in their support channels, or their social media channels if they have any.
  5. Is there any mitigation for the issue?

    • Understand if there are workarounds or mitigations for the issue. Can you use a different provider? Is the switch easy to do? Talk with your team to understand the best course of action.
    • Need to wait on the service provider to fix the issue? Understand if there is a timeline for the fix. Adapt your communication with your team and users to the situation. It's very important to keep everyone informed.
  6. Did GitHub Webhooks recover?

    • Continue to monitor the situation. A lot of times, the service can see a brief recovery and declare the issue as resolved, but it can come back. Keep monitor for some time to make sure it's really resolved.
  7. Post-incident analysis

    • Once the issue is resolved, it's important to do a post-incident analysis. Understand what went wrong and if it's possible or needed to do something to prevent it from happening again.
    • Sometimes if it's a critical dependency, you might need to have a backup plan in place to avoid a similar issue.
    • Vendors usually publish post-mortem analysis reports, so keep an eye on their social media channels and website for more information.
  8. Prepare for the next incident, because it will happen again

    • Start monitoring your dependencies. Sign up to IsDown and aggregate all your dependencies status in one place.
    • Nowadays, it's very common to have a lot of dependencies, and keeping an eye on them is not an easy task. IsDown can help you with that, by aggregating and monitoring all dependencies status and alerting you if they are having issues. Create status pages to communicate with your team and users.
    • For a complete overview of GitHub’s status across all services, including repositories, API requests, and workflows, visit the GitHub Status Page on IsDown

Want to be informed about GitHub status changes?

IsDown offers an easy way to monitor GitHub with maximum flexibility

Major Outages Notifications

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.

Minor Outages 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.

Outage Details

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.

Maintenance Feed

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.

Component Filtering

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.

Early Outage Indicators

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.

Frequently Asked Questions

How can I check the status of GitHub Webhooks?

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.

Why are my webhook deliveries delayed or not arriving?

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.

Are there known issues with webhook events and payloads?

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.

How do I validate GitHub Webhook deliveries during an outage?

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.

What should I do if my repository webhook is not triggering?

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.

Can I manually trigger or test GitHub Webhooks if there is a service disruption?

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.

Is GitHub Webhooks slow today?

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.

How are GitHub Webhooks outages detected?

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.

When was the last GitHub Webhooks outage?

GitHub Webhooks last outage was on March 20, 2025 with the title "Incident with Pages"

GitHub not working for you? How do I know if GitHub is down?

  • Check on the top of the page if there are any reported problems by other users.
  • Find their support at their official website.
  • Find their support contact at their official status page.

How IsDown compares to DownDetector?

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.

Never again lose time looking in the wrong place

14-day free trial · No credit card required · No code required