GitHub Status History Scraper

GitHub Status History Scraper

Scrape GitHub Status history into clean incident records. Every incident comes with its status, impact, timestamps, and affected components. No API key. Export to CSV, JSON, Excel, or XML.

GitHub's status page shows current and past incidents, but there is no official API for historical data. This Actor reads the public status page directly and returns each incident as a flat row, so you can track uptime, review past outages, or feed your own monitoring dashboards.

Who uses it	What they scrape GitHub Status for
SRE and DevOps teams	Monitor GitHub service reliability and correlate with internal incidents
Developer experience managers	Report on third-party dependency uptime for stakeholders
Data analysts	Build historical datasets of GitHub outages for trend analysis
Compliance officers	Document service availability for audits and SLAs

What it does

This Actor collects GitHub Status incidents, scheduled maintenances, and component statuses, and returns each record as a flat row.

• 📋 Five export modes: overall summary, all recent incidents, unresolved incidents, scheduled maintenances, or components list.
• 📅 Date filtering: return only incidents created on or after a given ISO date.
• 🔍 Component filtering: keep only records affecting components whose name contains a given string, like 'Actions' or 'Pages'.
• 📦 Flat output: every incident is one row with status, impact, timestamps, and affected components.

Results export to CSV, JSON, Excel, or XML, or straight from the API.

What you can do with GitHub Status data

📈 Track GitHub uptime over time.

An SRE runs the Actor weekly in 'incidents' mode and appends the results to a database to chart GitHub availability and spot recurring problems.

🔔 Monitor unresolved incidents.

A DevOps engineer schedules the Actor in 'unresolved' mode every hour and pipes the output into a Slack alert when a new incident appears.

📊 Report on third-party dependencies.

A developer experience manager exports all incidents from the last quarter and includes the data in a stakeholder report on external service reliability.

🧾 Audit service history for compliance.

A compliance officer pulls the full incident history with component filters to document GitHub availability for an audit.

Why choose this scraper

	What you get
No API key	Reads the public status page directly, no registration or token needed
Historical data	Get past incidents, not the current status
Structured output	Clean rows ready for CSV, JSON, Excel, or XML
Flexible filters	Limit by date or component to focus on what matters

How it compares

No other Store actor targets GitHub Status the same way, so the honest comparison is with the alternatives teams actually weigh.

	GitHub Status History Scraper	Build it in-house	By hand
Setup	Run it now, zero config	Days of engineering	None, but hours per pull
When GitHub Status changes	Maintained for you	You fix it	You re-learn the page
Proxies, retries, anti-bot	Built in	Your problem	Browser only
Output	Fixed JSON schema, CSV/Excel export	Whatever you build	Copy-paste
Cost	Pay per result	Engineering time	Analyst hours

Configure the run

Pick a mode, set an optional start date, and filter by component name. The Actor reads the public status page and returns only the records that match. The Input tab lists every parameter.

A first run with the defaults:

{
 "maxItems": 10,
 "mode": "incidents"
}

A larger pull:

{
 "maxItems": 200,
 "mode": "incidents"
}

Pricing

Pay-per-result: $0.01467 per result collected. You pay only for the results written to your dataset.

Results collected	Approximate cost
100 results	$1.47
1,000 results	$14.67
10,000 results	$146.70

New Apify accounts start with $5 in free credit.

Free users

Free-plan runs return up to 10 results as a preview. Upgrade your Apify plan to collect up to 1,000,000 results per run.

Run it

1. Create a free Apify account with $5 in credit.
2. Open the GitHub Status History Scraper.
3. Set your inputs and any filters, then click Start.
4. Export the results as CSV, Excel, JSON, or XML from the Dataset tab.

Run it programmatically through the Apify API (run-sync-get-dataset-items) or the ApifyClient for JavaScript and Python.

Use with AI agents (MCP)

Give an AI agent live access to GitHub Status through the Model Context Protocol. Add the Actor to Claude, Cursor, or any MCP client:

$claude mcp add --transport http apify "https://mcp.apify.com?tools=parseforge/github-status-history-scraper"

Then prompt it in plain language to run the scraper and read back the results.

Troubleshooting

Why am I getting no results?

Check your filters. If you set a 'Since' date in the future or a 'Component Filter' that matches nothing, the Actor will return an empty dataset. Try removing filters or broadening the component string.

The Actor returns fewer incidents than expected.

The 'Maximum incidents' input limits the number of records. Increase it if you need more. Also, the status page may only show a certain number of recent incidents.

I get an error when running the Actor.

Ensure your 'Since' date is a valid ISO date string like '2026-01-01'. If the problem persists, check the Actor log for details and try again later, as the status page may be temporarily unavailable.

The component filter is not working as expected.

The filter is case-insensitive and matches any part of the component name. For example, 'actions' will match 'GitHub Actions'. If you still get no results, verify the component name on the GitHub Status page.

Can I get real-time alerts for new incidents?

This Actor is designed for on-demand or scheduled scraping. For real-time alerts, schedule it frequently (e.g., every minute) and use a webhook or integration to notify you when a new unresolved incident appears.

FAQ

Question	Answer
Does this Actor need a GitHub API token?	No. It reads the public GitHub Status page directly, so no authentication or API key is required.
Can I get historical incidents, not the current status?	Yes. Use the 'All Recent Incidents' mode and optionally set a 'Since' date to retrieve incidents from a specific period.
What is the difference between 'incidents' and 'unresolved' modes?	'Incidents' returns all recent incidents, including resolved ones. 'Unresolved' returns only incidents that are still ongoing.
How do I filter by a specific GitHub service, like Actions or Pages?	Use the 'Component Filter' input. The Actor will only return records where the affected component name contains the string you provide.
What output formats are supported?	You can export the results as CSV, JSON, Excel, or XML directly from the Apify dataset.
Can I schedule this Actor to run automatically?	Yes. Use Apify's scheduler to run it at any interval, such as every hour or daily, and store the results in a dataset or send them to a webhook.
Does the Actor return the full incident description?	Yes, each incident record includes the status text, impact level, timestamps, and affected components as provided on the status page.
Is there a limit on how many incidents I can retrieve?	You can set 'Maximum incidents' up to 1,000,000 per run. The default is 10.
What is the 'Components List' mode?	It returns the current status of all GitHub components, such as 'API Requests', 'Actions', and 'Pages', with their individual statuses.
Can I use this data for commercial purposes?	The data comes from GitHub's public status page. Please review GitHub's terms of service for any restrictions on use.

Related actors

Browse the full ParseForge collection for more scrapers.

🆘 Need help? Email parseforge@protonmail.com with your run ID, your input, and what you expected.

⚠️ Disclaimer. This Actor is unofficial and is not affiliated with, endorsed by, or sponsored by GitHub, Inc. It collects only publicly available data. You are responsible for using the collected data in compliance with the source's terms of service and applicable data-protection laws, including GDPR, CCPA, and PIPL. Do not use it to collect personal data unlawfully.