outages.live
Live

Northflank

Northflank is reporting major outage

Checked 11 s ago Major outage

Security incident

Northflank reports a security incident that affects Networking, Certificates, Services, Addons, Jobs, Builds, and Logs and Metrics. The impact is a major outage. Northflank has identified the incident.

Major outageupdated 2 h ago

History

90 days agoToday

Incidents in 90 days

1

Days with an incident

3

Median duration

No data

Longest incident

No data

Components

11

Northflank Platform

Networking Major outage
90 days ago3 days with an incidentToday
Certificates Major outage
90 days ago3 days with an incidentToday
Services Major outage
90 days ago3 days with an incidentToday
Addons Major outage
90 days ago3 days with an incidentToday
Jobs Major outage
90 days ago3 days with an incidentToday
Builds Major outage
90 days ago3 days with an incidentToday
Logs and Metrics Major outage
90 days ago3 days with an incidentToday
Northflank App Operational
90 days agoNo incidentsToday
Northflank API Operational
90 days agoNo incidentsToday
Marketing Site Operational
90 days agoNo incidentsToday
Documentation Operational
90 days agoNo incidentsToday

Past incidents

Provider status pageTimes in UTC

No incident in the last 90 days.

Affected components

7
  • NetworkingNorthflank PlatformMajor outage
  • CertificatesNorthflank PlatformMajor outage
  • ServicesNorthflank PlatformMajor outage
  • AddonsNorthflank PlatformMajor outage
  • JobsNorthflank PlatformMajor outage
  • BuildsNorthflank PlatformMajor outage
  • Logs and MetricsNorthflank PlatformMajor outage

Follow Northflank

Your coding agent knows when Northflank is down, and tells you when a failure is theirs, not yours. You can also get Northflank incidents in a feed reader or in Slack.

Prompt
Install the outages.live MCP server, so that when something breaks you can tell if the cause is a provider we depend on and not my code. It reads the official status pages of cloud, AI, payment and developer providers and gives you their incidents as MCP tools.

Add it as a remote MCP server named "outages" at https://outages.cc/mcp (Streamable HTTP, no authentication), with your CLI command or your MCP config file.

Then:
1. Make sure it connects and shows the tools get_provider, list_feed and send_feedback.
2. Call get_provider with "northflank" and tell me if Northflank has a problem right now.
3. From now on, when a call to a third-party service fails or becomes slow, call get_provider for that service before you change my code.

Paste this into any coding agent. It adds the server with its own MCP setup.

RSS
https://outages.cc/feed.xml?providers=northflank
Slack
/feed subscribe https://outages.cc/feed.xml?providers=northflank

Go from tracking outages to fixing production issues with Polylane.

Try Polylane