FreeClimb Outage History

FreeClimb is up right now

FreeClimb had 2 outages in the last 2 years totaling 6h 4m of downtime — averaging 0.1 incidents per month.

There were 2 FreeClimb outages since October 24, 2024 totaling 6h 4m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.freeclimb.com

Minor April 1, 2026

10DLC Messaging Delivery Impact

Detected by Pingoru
Apr 01, 2026, 02:19 PM UTC
Resolved
Apr 01, 2026, 08:23 PM UTC
Duration
6h 4m
Affected: Inbound SMS (Long Code)Outbound SMS (Long Code)
Timeline · 4 updates
  1. investigating Apr 01, 2026, 02:19 PM UTC

    An SMS provider upstream to FreeClimb is currently experiencing issues with sending and receiving 10DLC SMS/MMS messages. The issue is being investigated.

  2. investigating Apr 01, 2026, 05:02 PM UTC

    The upstream provider continues to investigate the issue causing SMS/MMS failures, we will continue to provide updates as they are available.

  3. monitoring Apr 01, 2026, 06:06 PM UTC

    The upstream SMS provider has identified and corrected the issue causing messages to not be sent or be delayed in sending. During this time messages were queued and are now being sent. The situation will continue to be monitored.

  4. resolved Apr 01, 2026, 08:23 PM UTC

    10DLC Messaging Incident resolved Our team has continued to observe normal messaging send/receive times. At this time messing functionality has been fully restored. If you experience any issues please open a ticket by emailing [email protected].

Read the full incident report →

Notice October 24, 2024

Messaging impact due to upstream provider incident

Detected by Pingoru
Oct 24, 2024, 09:30 PM UTC
Resolved
Oct 24, 2024, 09:30 PM UTC
Duration
—
Timeline · 1 update
  1. resolved Oct 25, 2024, 05:31 PM UTC

    From approximately 15:30-17:00 CT on Thursday, October 24, one of FreeClimb's upstream messaging providers experienced a partial outage and some outbound/inbound messages may have failed during this time. The problem was resolved and service is working as expected now.

Read the full incident report →