Spikes in system load on DO monitoring graphs

Ive noticed over the past 6 hours, a number of times, the DigitalOcean monitoring graphs are showing spikes of system load from 1 up to around 60, then a few minutes later dropping back to normal again. During these load peaks the memory drops to 0 and some CPU spike also.

Ive noticed this across a number of my droplets around the same times today. Is this something I should look into? I dont think the site went down , not long enough to trigger an alert anyway

Submit an answer

This textbox defaults to using Markdown to format your answer.

You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!

Sign In or Sign Up to Answer

These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.

Want to learn more? Join the DigitalOcean Community!

Join our DigitalOcean community of over a million developers for free! Get help and share knowledge in Q&A, subscribe to topics of interest, and get courses and tools that will help you grow as a developer and scale your project or business.

I’m also having this issue and was concerned something was going wrong but it is reassuring I’m not the only person having this problem with the monitor. Hopefully it is just the monitor and nothing else?

I’m the same…

Assumed it was some sort of an attack. Would be nice if it was just an issue with the monitor.

I am also seeing this too. Hearing it happen to others makes me think it’s a monitoring/DO problem and not our servers. I’ve been monitoring via “htop” and my own logs, and have found nothing. Even during one the the actual spikes, I saw no change when SSH’d in. I imagine the the memory / cpu did actually hit 0, my programs would crash and I would see errors, but absolutely nothing.

I don’t really mind it, but it would be nice to get an official response as to what it is. If it’s a bug with monitoring, no problem, I’ll just keep that in mind.