Cool Ideas Fibre ISP – Feedback Thread 2

Status
Not open for further replies.

Seeyou

Expert Member
Joined
May 1, 2007
Messages
2,705
NY peering is up.

So for example:

198.27.85.92

From our London transit used to be:

2 100% 4 timeout
3 be100-1298.nwk-5-a9.nj.us 0% 3 200.1ms 200 199.9 200.1
4 be100-1323.bhs-g2-nc5.qc.ca 0% 3 208.9ms 209 208.9 209
5 100% 3 timeout
6 be7.bhs-s3-6k.qc.ca 0% 3 208.2ms 208.2 208.2 208.2
7 ns507973.ip-198-27-85.net 0% 2 208.1ms 208.1 208.1 208.1

So you would usually add another 140ms from Cape Town.

But now from Cape Town:

1 nyiix.nyc.ny.us 0% 4 190.5ms 190.4 190.1 190.6
2 be100-1323.bhs-g2-nc5.qc.ca 0% 4 199.3ms 199.3 199.2 199.5
3 100% 4 timeout
4 be7.bhs-s3-6k.qc.ca 0% 4 198.6ms 198.6 198.6 198.7
5 ns507973.ip-198-27-85.net 0% 4 198.4ms 198.5 198.4 198.6

This is apparently going to improve.

Next peer is IX.br which is the South America side of things.

Nice. Looking forward to S. America though. 200ms to New York is awesome, but 100ms to SA is actually playable latency for gaming.
 

Charmingmage10

Well-Known Member
Joined
Aug 6, 2015
Messages
206
NY peering is up.

So for example:

198.27.85.92

From our London transit used to be:

2 100% 4 timeout
3 be100-1298.nwk-5-a9.nj.us 0% 3 200.1ms 200 199.9 200.1
4 be100-1323.bhs-g2-nc5.qc.ca 0% 3 208.9ms 209 208.9 209
5 100% 3 timeout
6 be7.bhs-s3-6k.qc.ca 0% 3 208.2ms 208.2 208.2 208.2
7 ns507973.ip-198-27-85.net 0% 2 208.1ms 208.1 208.1 208.1

So you would usually add another 140ms from Cape Town.

But now from Cape Town:

1 nyiix.nyc.ny.us 0% 4 190.5ms 190.4 190.1 190.6
2 be100-1323.bhs-g2-nc5.qc.ca 0% 4 199.3ms 199.3 199.2 199.5
3 100% 4 timeout
4 be7.bhs-s3-6k.qc.ca 0% 4 198.6ms 198.6 198.6 198.7
5 ns507973.ip-198-27-85.net 0% 4 198.4ms 198.5 198.4 198.6

This is apparently going to improve.

Next peer is IX.br which is the South America side of things.

when will traffic be routed via sacs to NA-EAST?
 

leppie

Senior Member
Joined
Mar 25, 2019
Messages
563
NY peering is up.

So for example:

198.27.85.92

From our London transit used to be:

2 100% 4 timeout
3 be100-1298.nwk-5-a9.nj.us 0% 3 200.1ms 200 199.9 200.1
4 be100-1323.bhs-g2-nc5.qc.ca 0% 3 208.9ms 209 208.9 209
5 100% 3 timeout
6 be7.bhs-s3-6k.qc.ca 0% 3 208.2ms 208.2 208.2 208.2
7 ns507973.ip-198-27-85.net 0% 2 208.1ms 208.1 208.1 208.1

So you would usually add another 140ms from Cape Town.

But now from Cape Town:

1 nyiix.nyc.ny.us 0% 4 190.5ms 190.4 190.1 190.6
2 be100-1323.bhs-g2-nc5.qc.ca 0% 4 199.3ms 199.3 199.2 199.5
3 100% 4 timeout
4 be7.bhs-s3-6k.qc.ca 0% 4 198.6ms 198.6 198.6 198.7
5 ns507973.ip-198-27-85.net 0% 4 198.4ms 198.5 198.4 198.6

This is apparently going to improve.

Next peer is IX.br which is the South America side of things.

Now if Amazon peering can play along....
 

DeatheCore

Senior Member
Joined
Dec 4, 2006
Messages
847
Hi @PBCool hoping you can assist me with my ongoing issue with regards to packetloss on Vumatel? I feel that the issue is going nowhere.

#COOL-20190402-246535

After Gumani opened a ticket with Vumatel, I received a call from them, in which they were trying to tell me that small losses are normal and all other diagnostics are within spec from their side, and that I'm receiving the correct speed judging by the handover speedtest. Tried to explain to them that small local losses have a much larger impact on international throughput.

I feel like they're trying to find excuses to close the ticket - as in it could be my MikroTik router config, or CISP network issues. I've been doing tons of tests for the past few months including directly through the CPE so I know it's not my setup.

Is there anything you can do from your side to hand my tests on to a network engineer? Or someone who is not trying to find every possible reason that the loss is not originating from their side...

Not sure how exactly they find where the loss is coming from, but I feel that they need to start somewhere at least..
 

PBCool

Cool Ideas Rep
Company Rep
Joined
Jan 11, 2016
Messages
13,304
Hi @PBCool hoping you can assist me with my ongoing issue with regards to packetloss on Vumatel? I feel that the issue is going nowhere.

#COOL-20190402-246535

After Gumani opened a ticket with Vumatel, I received a call from them, in which they were trying to tell me that small losses are normal and all other diagnostics are within spec from their side, and that I'm receiving the correct speed judging by the handover speedtest. Tried to explain to them that small local losses have a much larger impact on international throughput.

I feel like they're trying to find excuses to close the ticket - as in it could be my MikroTik router config, or CISP network issues. I've been doing tons of tests for the past few months including directly through the CPE so I know it's not my setup.

Is there anything you can do from your side to hand my tests on to a network engineer? Or someone who is not trying to find every possible reason that the loss is not originating from their side...

Not sure how exactly they find where the loss is coming from, but I feel that they need to start somewhere at least..
This has been escalated to our SDM at Vumatel today. I will push from my side.
 
Status
Not open for further replies.
Top