Company Logo

Is there an Bugfender outage?

Bugfender status: Systems Active

Last checked: 7 minutes ago

Get notified about any outages, downtime or incidents for Bugfender and 1800+ other cloud vendors. Monitor 10 companies, for free.

Subscribe for updates

Bugfender outages and incidents

Outage and incident data over the last 30 days for Bugfender.

There have been 0 outages or incidents for Bugfender in the last 30 days.

Severity Breakdown:

Tired of searching for status updates?

Join OutLogger to be notified when any of your vendors or the components you use experience an outage. It's completely free and takes less than 2 minutes!

Sign Up Now

Components and Services Monitored for Bugfender

Outlogger tracks the status of these components for Xero:

Log ingestion API Active
Private instances (eu) Active
Private instances (us) Active
Public website (bugfender.com) Active
Support site (support.bugfender.com), email and chat Active
Web dashboard (dashboard.bugfender.com) Active
Component Status
Log ingestion API Active
Private instances (eu) Active
Private instances (us) Active
Public website (bugfender.com) Active
Support site (support.bugfender.com), email and chat Active
Web dashboard (dashboard.bugfender.com) Active

Latest Bugfender outages and incidents.

View the latest incidents for Bugfender and check for official updates:

Updates:

  • Time: June 26, 2024, 6:03 p.m.
    Status: Resolved
    Update: Logs are now being processed at the usual speed, so we're declaring the incident resolved. We will continue to monitor performance especially closely over the next hours. We're sorry for the inconvenience caused and we thank you for your patience.
  • Time: June 26, 2024, 5:46 p.m.
    Status: Monitoring
    Update: A fix has been implemented by our engineers, and we're catching up with the log queue. Logs are still being processed with delay, but no logs are lost.
  • Time: June 26, 2024, 4:25 p.m.
    Status: Identified
    Update: Our engineers are still working on the issue. Thank you for your patience.
  • Time: June 26, 2024, 2:54 p.m.
    Status: Identified
    Update: We have identified the issue in a database server that's not working. Our engineers are looking into it. Log processing speed has recovered somewhat, but still below our 2-minute objective.
  • Time: June 26, 2024, 2:44 p.m.
    Status: Investigating
    Update: Our log processing infrastructure is running behind which is causing that the logs sent to our servers are not shown in the dashboard. No logs have been lost, and we're working to process them as soon as possible.

Updates:

  • Time: June 13, 2024, 9:50 a.m.
    Status: Resolved
    Update: After a more thorough investigation, this was a monitoring failure and we can not identify any issues with the service performance. We will continue to monitor closely for the next hours, but it looks like a false alarm.
  • Time: June 13, 2024, 9:26 a.m.
    Status: Investigating
    Update: Our log processing infrastructure is running behind which is causing that the logs sent to our servers are not shown in the dashboard. No logs have been lost, and we're working to process them as soon as possible.

Updates:

  • Time: May 31, 2024, 4:03 p.m.
    Status: Resolved
    Update: The incident has been resolved. Thanks for your patience, and sorry for the inconvenience caused.
  • Time: May 31, 2024, 3:30 p.m.
    Status: Monitoring
    Update: Our engineers identified the problem and applied a fix. We're currently monitoring.
  • Time: May 31, 2024, 3:21 p.m.
    Status: Investigating
    Update: We're experiencing an elevated level of API and Dashboard errors, and are currently looking into the issue.

Updates:

  • Time: March 6, 2024, 9:47 a.m.
    Status: Resolved
    Update: This incident has been resolved, and all systems are now operational. Please note that there may be some pending logs to be processed, so expect a delay in logs appearing as the systems process all pending information.
  • Time: March 6, 2024, 8:43 a.m.
    Status: Monitoring
    Update: The issue has been traced to a power outage in our main datacenter. Backup infrastructure has been activated, and services are mostly fully functional. However, please be advised that performance may be degraded, and some intermittent outages may occur while everything comes back to a stable state.
  • Time: March 6, 2024, 7:41 a.m.
    Status: Monitoring
    Update: A new fix has been implemented, and we are currently monitoring the results. Please be aware that intermittent outages may occur as our engineers continue to work on the system.
  • Time: March 6, 2024, 7:26 a.m.
    Status: Identified
    Update: The in-place fix did not resolve the issue. Our engineers are continuing to work on finding a viable alternative.
  • Time: March 6, 2024, 7:04 a.m.
    Status: Monitoring
    Update: A fix has been implemented, and we are currently monitoring the results. Please be aware that intermittent outages may occur as our engineers continue to work on the system.
  • Time: March 6, 2024, 6:28 a.m.
    Status: Identified
    Update: The issue has been identified. We expect to restore normal service shortly.
  • Time: March 6, 2024, 5:06 a.m.
    Status: Investigating
    Update: We are continuing to investigate this issue.
  • Time: March 6, 2024, 5:05 a.m.
    Status: Investigating
    Update: We are currently experiencing an unexpected outage at our datacenter affecting all services. Our team is actively investigating the issue and working to restore services as quickly as possible. We apologize for the inconvenience and appreciate your patience. Updates will be provided as soon as more information is available.

Updates:

  • Time: Feb. 26, 2024, 3:25 p.m.
    Status: Resolved
    Update: The following devices stopped being able to send logs to Bugfender: * Android 7.0 and earlier * iOS 9.x and earlier * Windows 7 and earlier * Mac OS X 10.11 (El Capitan) and earlier * Firefox 49 and earlier Our SSL certificate provider, Let's Encrypt, uses a new root certificate (ISRG Root X1), which is not installed by default in the above listed devices. If you can configure the devices, like in the case of a kiosk application or MDM-enrolled devices, you can manually trust the ISRG Root X1 certificate listed here: https://letsencrypt.org/certificates/ If you want to see the devices affected in an application, you can check the "Device Config." tab, and use the "OS Version" filter to find the devices under those versions. Devices affected are 7.0 and older (but not 7.1 and newer). We expect the impact of this transition to be minimal, since Android 7.0 devices have been out of official support for a long time and many applications no longer work there. If you have any further questions, please contact us at support.bugfender.com or via the chat, and we'll be happy to help you.

Check the status of similar companies and alternatives to Bugfender

Hudl
Hudl

Systems Active

OutSystems
OutSystems

Systems Active

Postman
Postman

Systems Active

Mendix
Mendix

Systems Active

DigitalOcean
DigitalOcean

Systems Active

Bandwidth
Bandwidth

Systems Active

DataRobot
DataRobot

Systems Active

Grafana Cloud
Grafana Cloud

Systems Active

SmartBear Software
SmartBear Software

Systems Active

Test IO
Test IO

Systems Active

Copado Solutions
Copado Solutions

Systems Active

CircleCI
CircleCI

Systems Active

Frequently Asked Questions - Bugfender

Is there a Bugfender outage?
The current status of Bugfender is: Systems Active
Where can I find the official status page of Bugfender?
The official status page for Bugfender is here
How can I get notified if Bugfender is down or experiencing an outage?
To get notified of any status changes to Bugfender, simply sign up to OutLogger's free monitoring service. OutLogger checks the official status of Bugfender every few minutes and will notify you of any changes. You can veiw the status of all your cloud vendors in one dashboard. Sign up here
What does Bugfender do?
Bugfender is a log storage service that helps application developers resolve bugs more effectively and provide better customer support with full logs.