No reported issuesAn email when it goes down, and when it’s back.
As of 03:36 UTC on 12 November 2026, iD4me's status page reports no issues. Its last reported problem was on 27 September 2026: “id4me.me, id4me-service and 1 more are down”, critical, for at least 2 h 52 min from 19:49 UTC.
- Last problem
- 27 Sept · ≥ 2 h 52 min
- Problems, last 30 days
- 0
- Typical incident
- 2 h 52 min
- Longest in 90 days
- None yet
Uptime
iD4me, last 30 days
100 %
No downtime in the last 30 days.
Incidents
Started in the last 7 days
0
This week Week before
No incidents in the last 60 days.
Recovery
Median time back online
None yet
Nothing started and ended in the last 30 days.
Components 3
All online
System Status 1
part 
- id4me.me
Service 1
part
- id4me-service
signup.id4me.me 1
part
- signup.id4me.me
Last 90 days
1 incident in 47 days tracked · no reported issues 98.5% of the time · typical incident 2 h 52 min
Recent incidents
Times in UTC
- id4me.me, id4me-service and 1 more are down at least 2 h 52 min
Critical
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 iD4me’s official status page at status.id4me.me every 5 minutes and keeps 90 days of what changed. We don’t test iD4me ourselves, so a problem shows here once iD4me reports it.
Stackpulse isn’t affiliated with iD4me. 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.