Incident history

Email

Updates go to your inbox. We'll send one confirmation email first.

Webhook — for agents and automation

We POST signed JSON (Standard Webhooks) for incident, maintenance and component status events.

1. We first send a subscription.verify event with a challenge to your URL.
2. Reply 2xx with the challenge in the body (plain text or {"challenge":"…"}).
3. You get a signing secret to verify webhook-signature headers, and a manage token to unsubscribe.

{
  "type": "incident.created",
  "timestamp": "2026-10-09T12:04:00Z",
  "page": {
    "id": "pg_1k62abasp0mvcafv7a2",
    "name": "Gitfence",
    "url": "https://status.gitfence.dev"
  },
  "incident": {
    "id": "inc_…",
    "title": "Elevated error rate",
    "status": "investigating",
    "impact": "major",
    "components": [
      {
        "key": "api",
        "status": "partial_outage"
      }
    ]
  }
}

Slack

Paste an incoming webhook URL (Slack app → Incoming Webhooks). We'll post a test message right away.

Discord

Paste a webhook URL (Channel settings → Integrations → Webhooks). We'll post a test message right away.

Telegram

Get updates in a Telegram chat or group from the UpButler bot. No bot of your own needed.

Feeds

Follow incidents in a feed reader, or poll the JSON from a script.

RSS  https://status.gitfence.dev/feed.rss

Atom https://status.gitfence.dev/feed.atom

JSON https://status.gitfence.dev/status.json