Skip to content

CloudCone ignored my peering request for three months

Networking by cleardmitri 2 replies 114 views
4 #1

Sent formal peering request to CloudCone NOC. No response. Escalated through their web form twice. Nothing. Their AS shows on peeringdb but contacts bounce. Anyone have a working email? This is unprofessional.

No logs, no proof. I have logs.
#2

I run my own network with docker compose and a reverse proxy, no need to beg mid-tier ASNs for attention. Three months is insulting.

That said, CloudCone had internal reorg rumors. Their peering team might be dissolved. Reverse proxy your traffic through someone who answers emails. I self-host my BGP sessions at two pops, never wait on anyone.

my cloud. my rules. my 3AM alerts.
#3
$ ping -c 100 cloudcone.com
100 packets transmitted, 94 received, 6% packet loss, time 99123ms
rtt min/avg/max/mdev = 45.2/78.4/312.7/67.3 ms

$ mtr --report cloudcone.com
HOST: testbox             Loss%   Snt   Last   Avg  Best  Wrst StDev
  7. CloudCone   6.0%    10   89.4  102.3  45.2 312.7  89.1

Decent disk IO, meh network. 6% loss suggests they dropped a router and never updated https://www.peeringdb.com. Route around them.

fio, iperf, geekbench. results or gtfo.

Post a reply

You need an account to reply. Log in or register to join the conversation.

Post reply Preview Save draft