Skip to main content
Graphite logo

Is Graphite Down?

No — Graphite is up

Reachable from all 8 checked regions

Average response time: 182ms

Last checked · checks run every 6 hours

Official status page: https://status.graphite.com

Graphite uptime

100%
Last 7 days
100%
Last 30 days
100%
Last 90 days
210ms
Avg response, 30 days

Measured from multiple regions every 6 hours. Percentages count only checks that returned an availability answer — 18 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.

30-day history

18-day clean streak
Sep 14: no data
Sep 15: no data
Sep 16: no data
Sep 17: no data
Sep 18: no data
Sep 19: no data
Sep 20: no data
Sep 21: no data
Sep 22: no data
Sep 23: no data
Sep 24: no data
Sep 25: no data
Sep 26: 100.00% uptime, 16 checks
Sep 27: 100.00% uptime, 32 checks
Sep 28: 100.00% uptime, 32 checks
Sep 29: 100.00% uptime, 32 checks
Sep 30: 100.00% uptime, 32 checks
Oct 1: 100.00% uptime, 30 checks
Oct 2: 100.00% uptime, 32 checks
Oct 3: 100.00% uptime, 32 checks
Oct 4: 100.00% uptime, 32 checks
Oct 5: 100.00% uptime, 32 checks
Oct 6: 100.00% uptime, 32 checks
Oct 7: 100.00% uptime, 32 checks
Oct 8: 100.00% uptime, 32 checks
Oct 9: 100.00% uptime, 32 checks
Oct 10: 100.00% uptime, 32 checks
Oct 11: 100.00% uptime, 32 checks
Oct 12: 100.00% uptime, 32 checks
Oct 13: 100.00% uptime, 32 checks
Sep 14 Today
No downtime Partial Downtime Not measurable No data

Reachability by region

Each region runs its own request from a different part of the world. A service can be up for one continent and down for another, which is usually the first sign of a routing or CDN problem.

ams
131ms
DNS 63ms TCP 2ms TLS 7ms TTFB 117ms
arn
121ms
DNS 55ms TCP 1ms TLS 7ms TTFB 110ms
cdg
100ms
DNS 62ms TCP 1ms TLS 3ms TTFB 88ms
dfw
232ms
DNS 82ms TCP 1ms TLS 4ms TTFB 176ms
ewr
182ms
DNS 110ms TCP 2ms TLS 4ms TTFB 160ms
fra
73ms
DNS 25ms TCP 1ms TLS 4ms TTFB 65ms
gru
421ms
DNS 372ms TCP 1ms TLS 5ms TTFB 414ms
iad
201ms
DNS 136ms TCP 2ms TLS 6ms TTFB 184ms

What Graphite does

Graphite is a code review tool for teams on GitHub; its old address, graphite.dev, redirects to graphite.com. Developers use its gt command-line tool to split work into stacks of small pull requests, then review them in the Graphite dashboard and PR inbox, land them through its stack-aware merge queue and get AI reviews. Every pull request it shows is a GitHub pull request.

What an outage looks like

The dashboard at app.graphite.com fails to load, the PR page or inbox errors or is slow, gt submit fails, or the merge queue stops landing PRs. Data can look out of date when Graphite falls behind on GitHub webhooks, as in April 2026. The status page splits Dashboard, CLI, Merge Queue, AI Reviews, Slack notifications and Docs, and has a separate GitHub row for upstream GitHub outages.

What to do about it

Check status.graphite.com and note whether the GitHub row is affected; if so, the problem is upstream, and Graphite points to GitHub's own status page. Your branches are ordinary git branches, so local git work continues. If your merge queue is not enforced, you can merge the bottom PR directly on GitHub, then run gt sync and gt submit. Report stuck CLI states with gt feedback.

Is it down for everyone, or just you?

If this page says Graphite is up but it is not loading for you, the problem is between you and them. Run a check against any URL from up to 17 cities across three regions to find out where it breaks.

Test it yourself

Related services

GitHub
GitHub
Slack
Slack
Linear
Linear
Cursor
Cursor

Graphite outage FAQ

Is Graphite down or is it GitHub?
Check the GitHub row on status.graphite.com first. Graphite is built on GitHub's APIs and GitHub is the only git provider it supports, so a GitHub outage breaks Graphite actions even when Graphite itself is healthy. Graphite posts these as incidents on its GitHub component, two of them lasting more than five hours in 2026, and links to GitHub's status page for updates.
Can I still merge pull requests when Graphite is down?
Often yes, through GitHub. Graphite's docs describe merging a stack by hand: merge the bottom PR on GitHub, run gt sync to pull trunk and restack, then gt submit, and repeat. The exception is a repository that enforces the Graphite merge queue through branch protection rules, where merging directly on GitHub is blocked until the queue is available again.
Does the gt CLI work when Graphite is down?
Partly. gt is fully compatible with git and passes commands like git add, git diff and git rebase straight through, so local commits and branches keep working. Creating or updating pull requests needs the CLI authenticated with your GitHub account, and Graphite tracks the CLI as its own status page component, so gt submit can fail during an incident.
Does a Graphite outage affect GitHub Enterprise Server?
Not when the outage is on github.com. Graphite's notices for GitHub outages in 2026 state that repositories hosted on-prem using GitHub Enterprise Server are not affected. Failures in Graphite's own Dashboard, CLI or Merge Queue are a separate matter, so check those rows on status.graphite.com as well.
Why is my Graphite PR data out of date?
Usually because Graphite has fallen behind on GitHub webhooks. Its GitHub App receives webhooks for CI status, mergeability and push events, and in April 2026 Graphite reported that data might be out of date due to delayed webhook processing. Graphite has also reported failures from hitting GitHub API rate limits, which can make some requests fail until it recovers.

How we measure this

  • We request Graphite's public endpoint every 6 hours from Fly.io regions across six continents — the most recent check ran from 8 of them.
  • A region counts as down only when it gets no usable HTTP response. A 403 or 429 means the origin answered and refused us, which we report as blocked, never as an outage.
  • A single failing region is treated as probe noise. We only change the verdict when two consecutive cycles agree.
  • Response times average only the regions that actually served the page, so a timeout never inflates the number.
  • Where Graphite publishes an official status feed we read it too. An all-clear from the vendor can soften an unconfirmed degradation; a vendor-declared outage only worsens our verdict when our own checks corroborate it.

Get alerted when Graphite goes down

This page refreshes every 6 hours. Your own monitors run as often as every 30 seconds, from up to 17 cities across three regions, and tell you the moment something breaks.

Start Free Monitoring
Free plan available No credit card required