This has been resolved. We were seeing a SYN flood targeting one of our internal message queues. This was preventing certain events being processed so whilst call-routing was unaffected, channel graphs in the portal will show a brief gap and certain API functions (for users hitting a particular node) would have returned an error code.
Posted about 1 year ago. Sep 18, 2017 - 02:15 UTC
A fix has been implemented and we are monitoring the results.
Posted about 1 year ago. Sep 18, 2017 - 01:44 UTC
We are presently mitigating a DDoS against our infrastructure. This is not affecting call traffic but has affected certain internal telemetry. More information to follow.