// Run global performance checks on HTTP endpoints from multiple regions worldwide. Use when users want to check speed, latency, performance, or test endpoints globally.
| name | global-speed-checker |
| version | 0.3.0 |
| description | Run global performance checks on HTTP endpoints from multiple regions worldwide. Use when users want to check speed, latency, performance, or test endpoints globally. |
Check HTTP endpoint performance from 28 regions worldwide.
Extract from user's message:
curl -s -L -X POST "https://openstatus.dev/play/checker/api?compact=true" \
-H "Content-Type: application/json" \
-d '{"url":"https://example.com","method":"GET"}'
The response contains newline-delimited JSON. Each line is a region result. Final line is the check ID.
Note: The compact=true parameter reduces response size by removing headers/body and returning calculated timing phases.
Parse the response (newline-delimited JSON) and create a markdown table sorted by latency (fastest first):
fra → "Frankfurt (Fly) 🇩🇪")timing object (e.g., DNS = dnsDone - dnsStart)**Fastest**: [region] ([latency]) • **Slowest**: [region] ([latency]) • **Average**: [avg]ms • **Success rate**: [x/y] ([%])
[View and share results](https://openstatus.dev/play/checker/[check-id])
Then ask: Would you like to see detailed insights or structured JSON data?
Analyze results (3-5 observations):
Provide complete results as structured JSON.
Common codes:
fra → Frankfurt (Fly) 🇩🇪iad → Virginia (Fly) 🇺🇸sin → Singapore (Fly) 🇸🇬lhr → London (Fly) 🇬🇧koyeb_fra → Frankfurt (Koyeb) 🇩🇪railway_us-west2 → California (Railway) 🇺🇸Full list: references/regions-detailed.md
Rate Limit (429): Show limit, remaining, reset time
Invalid Request (400): Show error message and details from response
No Client IP (400): Explain VPN/proxy may cause this
Design, scaffold, and contribute a community theme to openstatus (the open-source status page). Use whenever the user wants to create a new theme, customize status-page colors, build a palette for their brand, fork and contribute to openstatus's `@openstatus/theme-store`, or mentions OKLCH colors, CSS variables, or themes.openstatus.dev. Also use when the user pastes a theme export from the live explorer and wants it wired into the repo.
Build a custom status page UI using OpenStatus components or SDK. Use when someone wants to "create a status page," "build a status page," "integrate OpenStatus UI," "embed a status widget," "add status page components," or render monitors, incidents, and maintenance in their own app.
Write clear, empathetic incident status updates for any phase of an incident (investigating, identified, monitoring, resolved). Use when the user mentions "incident update," "status update," "outage communication," "write an incident," "investigating update," "post-incident update," or needs to communicate a service disruption to users.
Write planned maintenance announcements for each phase (scheduled, in-progress, completed). Use when the user mentions "maintenance announcement," "scheduled maintenance," "maintenance window," "planned downtime," "maintenance notification," or needs to communicate upcoming planned work to users.
Write blameless postmortems after incidents with timeline, root cause analysis, impact assessment, and action items. Use when the user mentions "postmortem," "post-mortem," "incident review," "root cause analysis," "RCA," "incident retrospective," "what went wrong," or wants to document lessons from a resolved incident.
Create or update the status page context document that all other status page skills reference. Use when setting up status page skills for the first time, or when the user mentions "status page context," "configure status page," "set up incident tone," or wants to define their service components, SLAs, or communication style.