Header Image
Active Incident

Updated a few seconds ago

For OCEAView application, please use https://oceaview.status.io/
DicksonOneDegraded Performance

Incident Status

Degraded Performance

Components

DicksonOne Device Communication

Locations

United States


March 4, 2026 9:26AM UTC
INVESTIGATING

We are currently experiencing a communication issue with RFL. Our team is actively investigating the problem.

DicksonOne Web Application




Operational

DicksonOne Device Communication




Degraded Performance

0

Upcoming Maintenances

1

Active Incidents

1

Maintenances Last 30 Days

History (Last 7 days)

DicksonOne Planned MaintenancePlanned Maintenance

Description

Scheduled maintenance is planned for the DicksonOne platform to enhance monitoring capabilities and reinforce system reliability. We anticipate minor system latency between 2:30 PM and 4:00 PM UTC. This maintenance is aligned with a required update from one of our infrastructure providers. To ensure continued platform stability, we are completing the work within this timeframe.


Components

DicksonOne Web Application, DicksonOne Device Communication


Locations

United States, Europe


Schedule

March 3, 2026 8:00AM - March 3, 2026 4:00PM UTC


March 3, 2026 2:39PM UTC
UPDATE

Maintenance has started.

March 3, 2026 2:39PM UTC
UPDATE

Maintenance has been completed.
DicksonOne Device Communication DisruptionOperational

Incident Status

Operational


Components

DicksonOne Device Communication


Locations

United States



February 27, 2026 2:53PM UTC
RESOLVED

Earlier today, beginning at approximately 1:00 AM CST (8:00 AM CET), we experienced a brief disruption in datapoint availability due to a database rebalancing process performed by our hosting provider. During this time, the API was intermittently unstable and datapoints were unavailable for approximately 5 minutes. Service quickly stabilized, and loggers resumed normal communication shortly thereafter. Any readings that were temporarily delayed were automatically transmitted once connectivity was fully restored. The overall system remained operational throughout the event. No data points were lost. A small number of customers may have received temporary “Not Reporting” alarms if their alarm thresholds were configured to trigger after a single missed reading. These alerts would have automatically cleared once communication normalized. The issue has been fully resolved and all monitoring processes have been restored.