KSeF status
All three environments are responding correctly. Invoice submission is running without disruptions.
Independent monitoring of the government KSeF 2.0 API, run by Biurko. We are not affiliated with the Ministry of Finance.
Environments
KSeF 2.0 API · probes every 5 minAvailability — last 90 days
Response time — last 24 h
Incidents and maintenance
RSSAll other days in this period: no incidents.
Don't want to keep checking this page?
Biurko sends invoices to KSeF for you — and watches the status so you don't have to. During an outage we queue your documents and retry automatically once KSeF is back.
What is KSeF and where does this data come from?
KSeF (Krajowy System e-Faktur) is the central e-invoicing system of the Polish Ministry of Finance, through which Polish businesses are required to issue structured invoices — the largest VAT payers from 1 February 2026, all remaining businesses from 1 April 2026. When KSeF is down, invoicing stops across Poland.
This page shows the results of our own probes: Biurko's backend sends an HTTP request to the government KSeF 2.0 API every 5 minutes and publishes the result of every attempt here — no sugar-coating.
Issue the invoice in offline24 mode and send it to KSeF no later than the next business day after the day of issue. The invoice is valid from the moment it is issued. In Biurko the app does that step for you: the QR code and the deadline for sending it on land on the invoice by themselves, the document waits in the queue, and we retry sending it once KSeF is back.
Biurko's backend sends an HTTP request to the government KSeF 2.0 API every 5 minutes and records the result and response time of each probe. We declare an outage after three consecutive failed probes and restore the operational status after two consecutive successful ones — this prevents isolated errors from triggering false alarms.
No. This is independent monitoring run by Biurko — a KSeF invoicing tool. Official announcements from the Ministry of Finance are published at ksef.podatki.gov.pl. When the Ministry announces an outage or maintenance, we record it in the timeline.
Yes — we probe all three environments: production, demo (pre-production) and test (anonymous integration testing). Demo and test matter mainly to integrators; production outages get priority because they affect real invoices.
The service responds, but slower than usual — response times exceed a threshold of roughly 2 seconds. Invoice submission still works, but may take longer or require retries. During an “Outage”, probes receive no valid response at all.
Probes run every 5 minutes, and the status changes after three consecutive failures — usually within about 15 minutes of the outage starting. Two consecutive successful probes restore the operational status. This rule protects against false alarms caused by isolated, transient errors.