GitHub Status Incident Snapshot
Pricing
from $240.00 / 1,000 incident reports
GitHub Status Incident Snapshot
GitHub Status incidents as published. Not a generated IR document from your traces. $0.01 / incident.
Pricing
from $240.00 / 1,000 incident reports
Rating
0.0
(0)
Developer
Zentra
Maintained by CommunityActor stats
0
Bookmarked
2
Total users
1
Monthly active users
2 days ago
Last modified
Categories
Share
GitHub Status incident titles. This does not draft an IR from your traces.
GitHub Status incidents as published. Not a generated IR document from your traces. $0.01 / incident.
Last run
Live row(s). First row: Degradation with Gemini 3.8 Flash
{"title": "Degradation with Gemini 3.8 Flash","entityName": "Degradation with Gemini 3.8 Flash","listingName": "Degradation with Gemini 3.8 Flash","productName": "Degradation with Gemini 3.8 Flash","sourceUrl": "https://stspg.io/hsjy12f57b24","sourceName": "GitHub Status incidents — not a generated IR document"}
Run it
{"searchKeywords": ["GitHub Status"],"sourceMode": "startUrls","outputMode": "buyer-ready-records","maxItems": 10,"startUrls": [{"url": "https://www.githubstatus.com/api/v2/incidents.json"}]}
What lands in the dataset
- GitHub Status incidents JSON
- incident name + status
- shortlink
Use it when
Snapshot incident names. Writing the postmortem is still yours.
On-call people who already read githubstatus.com incidents.
Price
$0.01 / incident — about $0.10 for a 10-row Try.
Schedule it. A one-off click is not Store revenue.
What you should know
- Not an incident writer.
- Overlaps GitHub Status components — this one is incidents.
FAQ
Is the last-run a fixture? No. If the dataset is empty, the public source failed — we do not invent a row.
Will this write my IR? No. It copies GitHub Status incident titles.