No reported issuesAn email when it goes down, and when it’s back.
As of 03:30 UTC on 12 November 2026, Pridok's status page reports no issues. Its last reported problem was on 15 October 2026: “Vi opplever tregheter for en andel av brukerne våre”, issue, for 2 h 18 min from 09:47 UTC.
- Last problem
- 15 Oct · 2 h 18 min
- Problems, last 30 days
- 1
- Typical incident
- 2 h 18 min
- Longest in 90 days
- 2 h 18 min · 15 Oct
Uptime
Pridok, last 30 days
99.67 %
Biggest dip: Pridok, 2.3 h of issue on Oct 15.
Incidents
Started in the last 7 days
0
This week Week before
No incidents this week. The last one: Pridok, issue on Oct 15.
Recovery
Median time back online
2 h 18 min
0 of 1 were over within an hour. Each dot is one incident; the dashed line is the median.
Components 6
All online
- Pålogging og nettsider
Andre tjenester 5
parts 
- Helsenorge og Pridok booking
- Meldingsutveksling
- Pridok API
- Eksterne integrasjoner
- Andre tjenester - Utskrifter, SMS-tjenester, rapporter m.v
Last 90 days
1 incident in 48 days tracked · no reported issues 99.8% of the time · typical incident 2 h 18 min
Recent incidents
Times in UTC
- Vi opplever tregheter for en andel av brukerne våre 2 h 18 min
Issue
Having issues right now
Paribu Humanity (H) Yatırma ve Çekme İşlemleri
CriticalAWS · Bahrain (me-south-1) Region Availability
CriticalAWS · UAE (me-central-1) Region Availability
CriticalGW Sistemas O componente “SAAS Webtrans” e alguns outros componentes estão Inativos
Critical
Popular services
All servicesWhere this comes from
Stackpulse reads Pridok’s official status page at status.pridok.no every 5 minutes and keeps 90 days of what changed. We don’t test Pridok ourselves, so a problem shows here once Pridok reports it.
Stackpulse isn’t affiliated with Pridok. Names and logos belong to their owners.
For agents and scripts
The same data as Markdown for AI agents, updated every 30 seconds. With Pro, the API and the MCP server give scripts and AI assistants every service and your own dashboards.