Spacebring Outage History

Spacebring is up right now

Spacebring had 12 outages in the last 2 years totaling 41h 36m of downtime — averaging 0.5 incidents per month.

There were 12 Spacebring outages since November 15, 2024 totaling 41h 36m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.spacebring.com

Minor May 20, 2026

Increased API error rates

Detected by Pingoru
May 20, 2026, 10:43 AM UTC
Resolved
May 20, 2026, 10:44 AM UTC
Duration
57s
Affected: Resources
Timeline · 2 updates
  1. investigating May 20, 2026, 10:43 AM UTC

    Our team is aware of this issue and is working to identify the cause. We will share updates as soon as we have more details.

  2. resolved May 20, 2026, 10:44 AM UTC

    The issue has been resolved, and all systems are now functioning normally. Thank you for your patience.

Read the full incident report →

Minor November 18, 2025

Certain third-party integrations affected by the Cloudflare outage

Detected by Pingoru
Nov 18, 2025, 02:28 PM UTC
Resolved
Nov 18, 2025, 08:05 PM UTC
Duration
5h 37m
Timeline · 3 updates
  1. identified Nov 18, 2025, 02:28 PM UTC

    Cloudflare, a major content delivery network, is currently experiencing a global outage. Spacebring is fully operational and unaffected. However, the Cloudflare disruption may impact the functionality of some integrations, such as the WayForPay payment gateway, which rely on Cloudflare's services. If you're experiencing issues with any integration, please refer to the official Cloudflare status page for the resolution updates: https://www.cloudflarestatus.com/.

  2. monitoring Nov 18, 2025, 05:39 PM UTC

    Cloudflare has implemented a fix. We are monitoring to confirm full stability across affected integrations.

  3. resolved Nov 18, 2025, 08:05 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor October 20, 2025

Degraded performance of Spacebring admin dashboard and member web portals

Detected by Pingoru
Oct 20, 2025, 01:27 PM UTC
Resolved
Oct 21, 2025, 06:28 AM UTC
Duration
17h 1m
Timeline · 2 updates
  1. monitoring Oct 20, 2025, 01:27 PM UTC

    Amazon Web Services (AWS), one of Spacebring's critical subcontractors, is currently experiencing a widespread outage. Due to this, Spacebring admin dashboard and member web portal may be temporarily unavailable or slow to respond. Some integrations with the affected services that rely on AWS, like Xero or some payment methods on Stripe, may not work. We are monitoring the situation, and once AWS resolves the issue on their end, the risk of a potential service outage will be removed.

  2. resolved Oct 21, 2025, 06:28 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor April 16, 2025

Customer credit balance doesn't update when permanent credits are given by administrator

Detected by Pingoru
Apr 16, 2025, 10:39 AM UTC
Resolved
Apr 16, 2025, 11:28 AM UTC
Duration
49m
Timeline · 2 updates
  1. identified Apr 16, 2025, 10:39 AM UTC

    Permanent credits added manually by administrators are not currently appearing in the credit balance of some customers. Our team is aware of this issue and is actively working to resolve it as soon as possible.

  2. resolved Apr 16, 2025, 11:28 AM UTC

    This issue has been resolved. Credit balances are now updated for affected customers and correctly reflect credits previously given. Thank you for your patience while we worked to fix this.

Read the full incident report →

Notice March 24, 2025

Gmail users may receive emails to Spam

Detected by Pingoru
Mar 24, 2025, 07:02 PM UTC
Resolved
Mar 25, 2025, 08:47 AM UTC
Duration
13h 45m
Timeline · 3 updates
  1. investigating Mar 24, 2025, 07:02 PM UTC

    Transactional emails sent from Spacebring to Gmail users may currently arrive in the Spam folder due to an issue on the side of our email provider, Postmark. The issue was identified at 11:03 EDT on March 24 and is under investigation by Postmark’s team. For updates on the resolution, please visit Postmark's status page: https://status.postmarkapp.com/notices/bt3ky3r8zlaapqlo-increased-gmail-spam-reports.

  2. monitoring Mar 25, 2025, 01:24 AM UTC

    A fix has been deployed by our email provider, Postmark, to remediate Gmail recipient emails going to spam. For updates on the resolution, please visit Postmark's status page: https://status.postmarkapp.com/notices/bt3ky3r8zlaapqlo-increased-gmail-spam-reports.

  3. resolved Mar 25, 2025, 08:47 AM UTC

    This issue has been resolved. For more details on the resolution, please visit Postmark's status page: https://status.postmarkapp.com/notices/bt3ky3r8zlaapqlo-increased-gmail-spam-reports.

Read the full incident report →

Minor February 10, 2025

When users sign up for a plan, their card was not saved as a default payment method

Detected by Pingoru
Feb 10, 2025, 09:32 PM UTC
Resolved
Feb 10, 2025, 09:32 PM UTC
Duration
Timeline · 1 update
  1. resolved Feb 10, 2025, 09:32 PM UTC

    When users signed up for a membership plan, their payment method was not saved as the default option, preventing automatic payment collection. While users could still pay their invoices manually, automatic payments with subscription renewals didn't happen due to the lack of a default payment method. This issue occurred across all gateway payment integrations that support card saving. We have identified the problem, resolved it for all future plan sign-ups, and designated all saved payment methods as the default for member profiles in locations using the Stripe and WayForPay payment gateway.

Read the full incident report →

Notice January 28, 2025

Users do not receive push notifications from Feed

Detected by Pingoru
Jan 28, 2025, 02:43 PM UTC
Resolved
Jan 28, 2025, 02:43 PM UTC
Duration
Timeline · 1 update
  1. resolved Jan 28, 2025, 02:43 PM UTC

    Members were experiencing issues with not receiving push notifications for new Feed posts and comments on posts in the Member Web Portal and Member Mobile App. This issue has now been resolved, and all members can receive push notifications from Feed, as expected.

Read the full incident report →

Minor January 8, 2025

Users do not receive push and email notifications

Detected by Pingoru
Jan 08, 2025, 04:55 PM UTC
Resolved
Jan 08, 2025, 05:16 PM UTC
Duration
21m
Timeline · 2 updates
  1. identified Jan 08, 2025, 04:55 PM UTC

    Users may currently experience issues with receiving notifications on both web and mobile. We have identified the problem and are actively working to resolve it. This problem affects both tracking notifications sent to administrators and account notifications sent to all users.

  2. resolved Jan 08, 2025, 05:16 PM UTC

    This incident has been resolved. Please note that all notifications that should have been received between 2:30 p.m. and 5 p.m. (UTC) on January 8, 2024, are not depicted on the Notifications page for administrators. Additionally, these notifications cannot be sent to users via push or email. Right now, all push and email notifications are sent successfully to users for actions that happen after 5 p.m. (UTC) time on January 8, 2024.

Read the full incident report →

Minor December 31, 2024

Issued invoices do not reflect the invoice items amount

Detected by Pingoru
Dec 31, 2024, 03:28 PM UTC
Resolved
Dec 31, 2024, 03:00 PM UTC
Duration
Timeline · 1 update
  1. resolved Dec 31, 2024, 03:28 PM UTC

    Manually created one-off invoices could show a zero amount next to each invoice item, but users could still see the correct total payable amount. This issue is now resolved. Users and administrators can reopen the invoice PDF on the web and mobile apps to see the updated amounts for each item.

Read the full incident report →

Notice December 10, 2024

Decreased size of the buttons on the web app opened on mobile devices.

Detected by Pingoru
Dec 10, 2024, 10:26 AM UTC
Resolved
Dec 10, 2024, 12:56 PM UTC
Duration
2h 30m
Timeline · 2 updates
  1. identified Dec 10, 2024, 10:26 AM UTC

    Users utilizing the web app on Android or iOS mobile devices may find that buttons at the bottom of the screen are cut in size or unnoticeable. We are aware of this issue and are working on improvements. Only users utilizing the web app on mobile devices are affected; those using the desktop version or the native mobile apps are not impacted.

  2. resolved Dec 10, 2024, 12:56 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice December 6, 2024

Users aren't synced to the access control group when the booking starts

Detected by Pingoru
Dec 06, 2024, 02:09 PM UTC
Resolved
Dec 06, 2024, 03:39 PM UTC
Duration
1h 30m
Timeline · 2 updates
  1. identified Dec 06, 2024, 02:09 PM UTC

    Users who book rooms or desks by paying through the online payment gateway are not being synchronized to the access control group, which prevents them from unlocking the doors. In contrast, users who pay for bookings with credits or create free bookings are successfully synced to the correct access control group. Additionally, granting access to users based on active subscriptions works properly. The Spacebring team has identified this issue with paid bookings and is actively working on a resolution.

  2. resolved Dec 06, 2024, 03:39 PM UTC

    The issue has been resolved. All users with current or future bookings have been synchronized to the relevant access group to unlock the doors during their booking duration, considering a 30-minute grace period.

Read the full incident report →

Minor November 15, 2024

Members see "The booking period is invalid" error while creating room bookings for future dates.

Detected by Pingoru
Nov 15, 2024, 09:57 AM UTC
Resolved
Nov 14, 2024, 07:00 PM UTC
Duration
Timeline · 1 update
  1. resolved Nov 15, 2024, 09:57 AM UTC

    Members may experience issues creating room bookings for future dates on the web and mobile. The values chosen in the "Book Ahead" set on the Desks page were used instead of the "Book Ahead" property for Rooms, which could cause error messages for members. The issue has been fixed and all the settings of the Rooms page apply for all the room bookings now.

Read the full incident report →