🐙 GitHub Status History Scraper

🚀 Export GitHub uptime and incident history in seconds. Pull live status, recent incidents, unresolved outages, scheduled maintenance, and component health across Git Operations, Actions, Pages, Packages, Webhooks, Issues, Codespaces, and more. No login, no manual page scrolling.

The GitHub Status History Scraper exports the live status page and returns 19 fields per record, including record type, incident name, severity impact, current status, monitoring and resolution timestamps, affected components, latest update text, update counts, and a permalink shortlink to the incident page. The underlying source is the official GitHub status feed powered by Statuspage.io and used by GitHub's own SRE team.

The dataset covers 19 monitored components (Git Operations, Actions, Packages, Pages, Webhooks, API Requests, Issues, Pull Requests, Codespaces, Copilot, GitHub Mobile, and more), the recent incident archive, unresolved incidents, and upcoming scheduled maintenance windows. This Actor turns that history into a downloadable dataset as CSV, Excel, JSON, or XML in under five minutes.

🎯 Target Audience	💡 Primary Use Cases
DevOps teams, SRE engineers, monitoring vendors, on-call leads, CI/CD platform owners, status-dashboard builders	Uptime dashboards, on-call paging, incident postmortems, vendor SLA tracking, multi-cloud status walls, deploy-window planning

📋 What the GitHub Status Scraper does

Five query workflows in a single run:

• 🚦 Overall summary. Current top-level status plus any open incidents.
• 🚨 All recent incidents. The full archive of recent outages and degradations.
• 🔧 Unresolved incidents. Only the incidents that are still active.
• 📅 Scheduled maintenances. Planned maintenance windows ahead of time.
• 🧩 Components list. Every monitored component with its current health.

Each record bundles type (incident, maintenance, component, summary), severity impact, lifecycle timestamps (created, updated, monitoring, resolved), affected component names and IDs, the latest status update text, and a direct shortlink to the incident on the status page.

💡 Why it matters: GitHub outages cascade into every team's CI pipeline, code review queue, and production deploy. Knowing about a degradation 30 seconds before the support tickets land is the difference between a calm rollback and a fire drill.

📊 Data fields

Each record includes: affectedComponents, componentIds, createdAt, id, impact, incidentImpact, latestUpdate, monitoringAt, name, recordType, resolvedAt, scheduledFor, scheduledStatus, scheduledUntil, scrapedAt, shortlink, status, updatedAt, updatesCount. These field names come straight from the actor's dataset schema, so what you see here is what lands in your dataset.

🚀 How to use

1. 📝 Sign up. Create a free account with $5 credit (takes 2 minutes).
2. 🌐 Open the Actor. Go to the GitHub Status History Scraper page on the Apify Store.
3. 🎯 Set input. Pick a mode (incidents, components, scheduled), and add optional date or component filters.
4. 🚀 Run it. Click Start and let the Actor collect your dataset.
5. 📥 Download. Grab results in the Dataset tab as CSV, Excel, JSON, or XML.

⏱️ Total time from signup to downloaded dataset: 3-5 minutes. No coding required.

🔗 Recommended Actors

• 📜 RFC Editor Index Scraper - IETF Internet standards catalog
• 🌐 IP Geolocation Scraper - Bulk IPv4/IPv6 geolocation lookups
• 📚 Internet Archive Search Scraper - 50M+ archived texts, audio, video, software
• ☁️ AWS Status Scraper - Live AWS service health and incidents
• 🌍 REST Countries Info Scraper - 250+ countries with population, currencies, languages

💡 Pro Tip: browse the complete ParseForge collection for more developer-tools scrapers.

⚠️ Disclaimer: this Actor is an independent tool and is not affiliated with, endorsed by, or sponsored by GitHub, Microsoft, or Statuspage.io. All trademarks mentioned are the property of their respective owners. Only publicly available status data is collected.

🆘 Need Help?

If you hit a bug, have questions about setup, or need a scraper we haven't built yet, open our contact form or write to parseforge@protonmail.com. We also take on paid custom data projects.

For faster answers, join our Discord. It's the best place to get support and suggest new actors.