GitfenceStatus
Live status · 2 components

All systems operational.

All systems operational

Updated 90-day uptimeIncident historyFor agents

Components

Uptime over the past 90 days
  • Website and appOperational
    90 days ago30 days ago100% uptimeToday
  • Git, MCP and APIOperational
    90 days ago30 days ago100% uptimeToday
For agents and automation
Read this page as JSON or MCP, or get signed webhooks when something changes.
What to do now: proceed, retry, fallback or pause (under 1 KB, no auth, cache 15s)
GET https://status.gitfence.dev/status.agent.json
JSON status (no auth, CORS enabled, safe to poll every 30s)
GET https://upbutler.com/api/v1/public/pages/gitfence
MCP: read-only server for this page
{
  "mcpServers": {
    "gitfence-status": { "url": "https://status.gitfence.dev/mcp" }
  }
}
// tools: get_verdict, get_status, list_incidents, subscribe_webhook
Webhook subscription (your endpoint must echo the challenge we send first)
curl -X POST https://upbutler.com/api/v1/public/pages/gitfence/subscribers \
  -H 'content-type: application/json' \
  -d '{"type":"webhook","url":"https://your-agent.example.com/hooks/status","components":["website-and-app"],"agent":"my-agent"}'
Paste into your agent
Subscribe to https://status.gitfence.dev status via webhook (POST https://upbutler.com/api/v1/public/pages/gitfence/subscribers, echo the verification challenge) and pause jobs that depend on Website and app when component "website-and-app" reports major_outage. Resume them when it is operational again.

Past incidents

Full history
Oct 16 – 29, 2026
No incidents reported.

Get Gitfence status updates

We'll notify you when an incident starts, changes or is resolved, and before maintenance.

Email

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

Only notify me about specific components

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.
Only notify me about specific components
Example event payload
{
  "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.

Only notify me about specific components

Discord

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

Only notify me about specific components

Telegram

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

Only notify me about specific components

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

For some components only, add ?components=website-and-app,git-mcp-and-api to an address.

Report a problem with Gitfence

Tell the team what isn't working. Your report goes to the team and is never shown publicly.

Only used to tell you once when this is fixed.