Status page
As a transparent company, we also share our incidents. Please let us know if anything is broken via our email. With us you don’t see days and days with “No issues today”. We just show the all incidents. No ways to trick you, we are not flawless.
Please contact us if anything is not working correctly via email or twitter
It's currently:
Homepage down
resolved Our homepage was down for approximately 30 minutes due to an attack that was being blocked by our service provider. The issue has been resolved and the homepage is now accessible again. Read more.
Custom domain data ingestion incident
resolved
Summary
We saw intermittent data ingestion for websites sending via a custom domain. A DDoS protection trigger at our hosting platform, Leaseweb, rate limited part of this traffic. The issue is now resolved.
Read more.
Data ingestion outage
resolved
We experienced a data ingestion outage starting at 2025-10-04 17:15:19 UTC.
During this period, incoming data was not received for 24 minutes.
Read more.
Short migration issue
resolved There is some data stored in the wrong database for less than 5 minutes. We expect this data to be showing up in the dashboard by tomorrow. It’s a very limited dataset and 66% of the data is moved into the wrong database. Read more.
Dashboard only downtime
resolved Our hosting provider is performing maintenance on the rack containing our server. This is causing downtime on our dashboard server. All data continues to be collected correctly. Read more.
Some visits tagged as robot
resolved We’ve identified that our advanced robot blocking feature is tagging too many visits as robot. We’re currently fixing this issue. No data is lost and it will appear in your dashboard a bit later. Only some users are affected. To verify if your data is coming in (including robots), please export the data with robot information included. Read more.
Degraded performance
resolved We identified that one of our systems caused certain requests to run extremely slowly, resulting in a large number of timeouts. We’ve implemented a hot fix, and since then, 100% of incoming data has been processed and stored successfully. Read more.
Degraded performance
resolved We experienced a brief disruption due to an unexpected surge in data volume, resulting in 25 minutes of downtime. The issue has been resolved, and we’re in the process of upgrading our cluster to better support future demand. These improvements will significantly enhance our ability to handle much larger data volumes moving forward. Read more.
Degraded performance
resolved We experienced some disruptions due to an influx of data at an unusually high volume. This occurred because a customer was sending data for numerous users every second. While we do have mechanisms to mitigate traffic from specific domains effectively, we managed to resolve the issue by . Read more.
Dashboard down time
resolved We had an issue with our dashboard script not loading correctly. We check with Hyperping, if our site is up and with many other alerts if the data is coming in. The issue here was that the dashboard data did load, but the JavaScript had a load error. Our uptime alerts missed this. Read more.
Custom domains not collecting data
resolved Our custom domain server was down and our hosting provider its’ customer dashboard was unavailable. This is an issue from our hosting provider Leaseweb. They have no incidents reported yet. Edit: they added a report now. Read more.
Dashboard and API not showing data
resolved On April 1st, we were not joking around. We had an issue where the data wouldn’t show up in the dashboard and API. New data was still being stored, but just not visible for our customers. We were able to fix the issue within one hour. The overview page with all your websites did catch up a bit later. It’s all back now. Read more.
Incorrect bot detection on Chrome mobile
resolved On June 18 we updated our public scripts. We did test with a few customers if the same amount of visits ended up in our database. This was the case. What we didn’t know was that we classified them as robots. We still store these visits as we want to show our customer how many visits came for robots for a better comparison with other analytics tools. It only effects visits from Chrome browsers on mobile. This includes Chrome for Android, Samsung Internet, UC Browser for Android, Microsoft Edge Mobile, and Opera Mobile. Your visits are not lost, they just don’t show up in the dashboard just yet. Read more.
DDOS mitigation in data center
resolved On March 1st at 12:05 PM UTC we had a network outage in our data center in Iceland. Our hosting provider suffered an attack, and have moved to DDOS mitigation. That’s why some of the requests didn’t succeed anymore. Read more.
Custom domain feature issue
resolved Some customers had issues with our custom domain feature. In your graph you could see some data changes (up or down) because of that issue. We had too many users using that feature (it’s popular) and it were to many for our server at that time. We fixed this issue as of 3th of March by moving that server away from Iceland to The Netherlands. Read more.
Lower visits tracked with public script
resolved As a transparent company, we also share our issues. On December 24th at 19:00 PM UTC we deployed a new version of our script to add the real time visits feature. We also added way more features in that script. After testing this in mulitple browsers we were confident that it was production ready. Read more.
Second network outage in data center
resolved As a transparent company, we also share our issues. On December 5th at 10:30 PM UTC we had a network outage in our data center in Iceland. We noticed this promptly with our monitoring systems and quick help from Daniel (our server hero). After 10 minutes our servers were reachable again and the outage was over. Read more.
First network outage in data center
resolved As a transparent company, we also share our issues. On July 11th at 6:10 PM UTC we had a network outage in our data center in Iceland. We noticed this promptly with our monitoring systems and quick help from Daniel (our server hero). After 46 minutes our servers were reachable again and the outage was over. Read more.
