Status unknownAn email when it goes down, and when it’s back.
As of 03:38 UTC on 12 November 2026, 365Tid Drifts's status page couldn't be read. It has reported no problems since Stackpulse started checking it.
- Last problem
- None since checks began
- Problems, last 30 days
- 0
- Typical incident
- None yet
- Longest in 90 days
- None yet
Uptime
365Tid Drifts, last 30 days
22.42 %
No incidents, only maintenance, 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 7
All online
365Tid 3
parts 
- 365Tid.dk
- 365tid App
- 365Tid API
EV Crono 4
parts
- Crono Web
- Crono App
- Crono API
- Synkronisering
Last 90 days
0 incidents in 48 days tracked · no reported issues 100% of the time
Recent incidents
Times in UTC
No incidents reported since Stackpulse started checking.
All incidents on 365tid.statuspage.io ↗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 services
Where this comes from
Stackpulse reads 365Tid Drifts’s official status page at 365tid.statuspage.io every few minutes and keeps 90 days of what changed. We don’t test 365Tid Drifts ourselves, so a problem shows here once 365Tid Drifts reports it.
Stackpulse isn’t affiliated with 365Tid Drifts. 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.