The Receptionist Outage History

The Receptionist is up right now

The Receptionist had 6 outages in the last 2 years totaling 260h 48m of downtime — averaging 0.2 incidents per month.

There were 6 The Receptionist outages since March 26, 2025 totaling 260h 48m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.thereceptionist.com

Major August 25, 2026

Issue Detected

Detected by Pingoru
Aug 25, 2026, 09:35 PM UTC
Resolved
Sep 02, 2026, 05:55 PM UTC
Duration
7d 20h
Timeline · 1 update
  1. resolved Sep 02, 2026, 05:55 PM UTC

    Our bot has informed us that things are back to normal! Please reach out if you are still experiencing any issues. Thanks!

Read the full incident report →

Major September 9, 2025

Email Notifications Issue

Detected by Pingoru
Sep 09, 2025, 12:43 PM UTC
Resolved
Sep 09, 2025, 05:54 PM UTC
Duration
5h 11m
Timeline · 1 update
  1. resolved Sep 09, 2025, 05:54 PM UTC

    We've now resolved the incident. Thanks for your patience. All queued emails that were not being sent as of last night have now been sent. All email services are now working as expected.

Read the full incident report →

Major June 26, 2025

Issue with SMS messaging

Detected by Pingoru
Jun 26, 2025, 04:07 PM UTC
Resolved
Jun 27, 2025, 03:40 PM UTC
Duration
23h 33m
Timeline · 1 update
  1. resolved Jun 27, 2025, 03:40 PM UTC

    The issue with SMS notifications has been resolved and messages should be sending as expected. Thank you for being patient as we worked through this issue with our text message carrier. If you experience any further issues, please contact support through the chat function or email us at [email protected].

Read the full incident report →

Major March 26, 2025

SMS Message not working

Detected by Pingoru
Mar 26, 2025, 07:59 PM UTC
Resolved
Mar 27, 2025, 07:44 PM UTC
Duration
23h 45m
Timeline · 1 update
  1. resolved Mar 27, 2025, 07:44 PM UTC

    Our SMS text notifications are now back online. Thank you for your patience as we worked to resolve this issue.

Read the full incident report →