Status unknownAn email when it goes down, and when it’s back.
As of 03:34 UTC on 12 November 2026, Wattsense's status page couldn't be read. Its last reported problem was on 7 October 2026: “Latency for box data processing”, issue, for 18 h 49 min from 12:47 UTC.
- Last problem
- 7 Oct · 18 h 49 min
- Problems, last 30 days
- 0
- Typical incident
- 18 h 49 min
- Longest in 90 days
- 18 h 49 min · 7 Oct
Uptime
Wattsense, last 30 days
99.51 %
No incidents, only maintenance, in the last 30 days.
Incidents
Started in the last 7 days
0
This week Week before
No incidents this week. The last one: Wattsense, issue on Oct 7.
Recovery
Median time back online
None yet
Nothing started and ended in the last 30 days.
Components 9
All online
- Console
- API
- Data Processing
Data Streams 2
parts 
- Webhooks
- MQTT (Cloud to Cloud)
Device connectivity 2
parts
- 4G connectivity
- Bridge/On Premise uplink activation
Data Storage 2
parts
- Data Archives
- Cloud Data storage
Last 90 days
1 incident in 48 days tracked · no reported issues 98.4% of the time · typical incident 18 h 49 min
Recent incidents
Times in UTC
- Platform update Maintenance updates 1 h
Maintenance - Latency for box data processing 18 h 49 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 services
Where this comes from
Stackpulse reads Wattsense’s official status page at status.wattsense.com every 5 minutes and keeps 90 days of what changed. We don’t test Wattsense ourselves, so a problem shows here once Wattsense reports it.
Stackpulse isn’t affiliated with Wattsense. 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.