Jump to content

Recommended Posts

Posted (edited)
Well it's been 3 days since our last issue so time to check in!

 

Today we seem to be locked out of the surfprotect panel (https://surfprotectpanel.exa.net.uk/panel/). It's returning HTTP 500 after logging in. Looks like more disruptions to our staff as we've been unable to unblock a site that was needed ASAP.

 

I'm getting the same issue. (we're on Surfprotect Quantum via Darklight)

 

The status page shows all operational.

https://status.exa.net.uk/

 

 

I've reported it to [email protected]

Edited by hallb15
  • Thanks 1
  • 3 months later...
Posted

What kind of ping times do you get to 8.8.8.8? We get 16ms with Exa on fibre 100 MB/s (BT 21CN). We were proviously getting 8ms when we were on BGfL 100Mb/s

 

I do like Surfprotect although on BGfL we had no control over what was blocked or not and no SSO with AD.

Posted (edited)

no issues for us since feb this year when fusion went t#$# up for about a week or so

if you contact support im sure they can unblock a site for you, a quick email gets stuff done the support guys are always helpfull.

Edited by round2it
  • Thanks 1
Posted
What kind of ping times do you get to 8.8.8.8? We get 16ms with Exa on fibre 100 MB/s (BT 21CN). We were proviously getting 8ms when we were on BGfL 100Mb/s

 

4ms here on Exa 100MB leased line

  • Thanks 1
Posted

Our ping to 82.219.4.24 was also 16ms

We are in Birmingham and I understand they have no datacentre nearby (yet) even though all Birmingham schools who were with the local authority are being migrated to Exa

 

Our traffic appears to route via oop north.

Posted (edited)

we are on EXA in Gloucester 100/100 LL

H:\>ping 82.219.4.24 -t

 

Pinging 82.219.4.24 with 32 bytes of data:

Reply from 82.219.4.24: bytes=32 time=6ms TTL=62

Reply from 82.219.4.24: bytes=32 time=44ms TTL=62

Reply from 82.219.4.24: bytes=32 time=57ms TTL=62

Reply from 82.219.4.24: bytes=32 time=39ms TTL=62

Reply from 82.219.4.24: bytes=32 time=45ms TTL=62

Reply from 82.219.4.24: bytes=32 time=30ms TTL=62

Reply from 82.219.4.24: bytes=32 time=45ms TTL=62

Reply from 82.219.4.24: bytes=32 time=38ms TTL=62

Reply from 82.219.4.24: bytes=32 time=17ms TTL=62

Reply from 82.219.4.24: bytes=32 time=26ms TTL=62

Reply from 82.219.4.24: bytes=32 time=8ms TTL=62

Reply from 82.219.4.24: bytes=32 time=13ms TTL=62

Reply from 82.219.4.24: bytes=32 time=26ms TTL=62

Reply from 82.219.4.24: bytes=32 time=17ms TTL=62

Reply from 82.219.4.24: bytes=32 time=28ms TTL=62

Reply from 82.219.4.24: bytes=32 time=23ms TTL=62

Reply from 82.219.4.24: bytes=32 time=6ms TTL=62

Reply from 82.219.4.24: bytes=32 time=12ms TTL=62

Reply from 82.219.4.24: bytes=32 time=15ms TTL=62

 

Ping statistics for 82.219.4.24:

Packets: Sent = 19, Received = 19, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 6ms, Maximum = 57ms, Average = 26ms

Control-C

Edited by k-strider
Posted

Interesting. For us, we see:

 

>ping 82.219.4.24
Pinging 82.219.4.24 with 32 bytes of data:
Reply from 82.219.4.24: bytes=32 time=7ms TTL=60
Reply from 82.219.4.24: bytes=32 time=7ms TTL=60
Reply from 82.219.4.24: bytes=32 time=7ms TTL=60
Reply from 82.219.4.24: bytes=32 time=6ms TTL=60

Ping statistics for 82.219.4.24:    
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:    
Minimum = 6ms, Maximum = 7ms, Average = 6ms

 

What traceroute do you get to that address?

Posted

Here is my tracert today

 

Tracing route to cache0.exa-networks.co.uk [82.219.4.24]
over a maximum of 30 hops:

 1    <1 ms    <1 ms    <1 ms  10.123.16.50
 2    10 ms     9 ms     9 ms  100.126.54.254
 3    10 ms    10 ms    10 ms  82.219.88.30
 4    16 ms    16 ms    16 ms  man-tcw-sr1.net.exa.net.uk [82.219.45.2]
 5    16 ms    16 ms    16 ms  r1.man-tcw.exa.net.uk [82.219.45.237]
 6    16 ms    16 ms    16 ms  cache0.exa-networks.co.uk [82.219.4.24]

Trace complete.

Posted
H:\>tracert 82.219.4.24

Tracing route to cache0.exa-networks.co.uk [82.219.4.24]
over a maximum of 30 hops:

 1     1 ms     1 ms     1 ms  10.7.58.60
 2    12 ms     3 ms     2 ms  gw.cryptschool.ce.exa.net.uk [82.219.30.62]
 3    26 ms    22 ms    17 ms  r1.man-tcw.exa.net.uk [82.219.43.52]
 4     5 ms     6 ms    10 ms  cache0.exa-networks.co.uk [82.219.4.24]

Trace complete.

Posted

Just tried it and got

Tracing route to cache0.exa-networks.co.uk [82.219.4.24]
over a maximum of 30 hops:

 1    <1 ms    <1 ms    <1 ms  xxx.xxx.xxx.xxx
 2    <1 ms    <1 ms    <1 ms  82.219.62.166
 3    <1 ms    <1 ms     2 ms  leeds-sc-sr1.net.exa.net.uk [82.219.45.224]
 4    <1 ms    <1 ms    <1 ms  r1.leeds-sc.exa.net.uk [82.219.45.245]
 5     1 ms    <1 ms    <1 ms  cache0.exa-networks.co.uk [82.219.4.24]

Trace complete.

Posted (edited)

Hmm...

 

We get 5 hops:

 

tracert 82.219.4.24

Tracing route to cache0.exa-networks.co.uk [82.219.4.24]
over a maximum of 30 hops:  
1    <1 ms    <1 ms    <1 ms  10.20.4.1  
2    <1 ms    <1 ms    <1 ms  10.10.0.1  
3    <1 ms    <1 ms    <1 ms  gw.mineheadmiddle.ce.exa.net.uk [82.219.52.142]  
4     9 ms     6 ms     6 ms  r2.lon-the.exa.net.uk [82.219.49.149]  
5     6 ms     6 ms     6 ms  cache0.exa-networks.co.uk [82.219.4.24]

So core switch, sophos UTM, their router on our site, their router at their DC, then their cache.

 

@Alis_Klar, you seem to have a device (100.126.54.254 in between your core and their supplier router adding 9ms to your connection times - I'd suggest that this is your issue. All the kit between an edge device and their router adds less than 1ms for me.

@k-strider, it seems odd that the time between your core and their router varies so much, from 2-12ms? Can't give an explanation for the increased times on their kit though there.

Edited by localzuk
Posted

 1     <1 ms    <1 ms    <1 ms  switch
 2    <1 ms    <1 ms    <1 ms  firewall
 3    <1 ms    <1 ms    <1 ms  router
 4     5 ms     5 ms     5 ms  82.219.74.84
 5     4 ms     4 ms     5 ms  cache0.exa-networks.co.uk [82.219.4.24]

 

From Nottingham.

 

1 ms = 300km, speed of light is mostly not an issue.

Posted

Light travels slower in fibre than it does in vacuum. That is why SpaceX's planned Starlink (low earth orbit satellites) will have a lower latency than existing trans-atlantic fibre routes. This is critial for high value financial transactions.

 

Posted
Light travels slower in fibre than it does in vacuum. That is why SpaceX's planned Starlink (low earth orbit satellites) will have a lower latency than existing trans-atlantic fibre routes. This is critial for high value financial transactions.

 

 

Only about 2/3rds though, won't affect our usage.

 

Some people were making a microwave network to go faster than fiber, mostly this shows that finance has gone off the rails and needs to be destroyed. When you're digging tunnels across the country to make networks 1ms faster so you can make the 1% even richer you've probably gone too far.

 

Meanwhile EXA can you work on your classifier a bit more, so many sites are wrongly classified, plus infinite reloads when it tries to classify a page that's offline, and the wrong website is shown when classifying a redirect.

 

Also something's hanging Chrome when I try to see the classification of a website in the portal system.

  • 5 weeks later...
Posted
Light travels slower in fibre than it does in vacuum. That is why SpaceX's planned Starlink (low earth orbit satellites) will have a lower latency than existing trans-atlantic fibre routes. This is critial for high value financial transactions.

 

 

Sorry wrong point in video linked. Correction

  • 1 month later...
Posted
Hi all,

 

Can anyone using Exa please try and download a file from dropbox.com? We just get 'unable to download the file'. Wondering if it's just us.

 

Just logged into my own account and "download"'d a file ok.

 

Peter

  • Thanks 1
Posted
Hi all,

 

Can anyone using Exa please try and download a file from dropbox.com? We just get 'unable to download the file'. Wondering if it's just us.

 

There is no issue that is affecting this from our side, so if I can ask you to give our support team a call on 0345 1451234 they will be able to take a look at this for you, or if you PM me your contact details I will get them to call you.

  • 2 months later...
Posted

Is this happening for anyone else?

 

tracert NOTLS.quantum.exa-networks.co.uk

 

Tracing route to NOTLS.quantum.exa-networks.co.uk [82.219.4.101]

over a maximum of 30 hops:

 

...

5 7 ms 8 ms 7 ms r2.man-tcw.exa.net.uk [82.219.44.2]

6 7 ms 6 ms 10 ms man-tcw-sr2.net.exa.net.uk [82.219.45.238]

7 8 ms 10 ms 6 ms brad-br-sr1.net.exa.net.uk [82.219.45.90]

8 6 ms 6 ms 6 ms brad-br-sr2.net.exa.net.uk [82.219.45.25]

9 8 ms 7 ms 5 ms leeds-sc-sr2.net.exa.net.uk [82.219.45.22]

10 25 ms 20 ms 18 ms r1.leeds-sc.exa.net.uk [82.219.45.247]

11 64 ms 45 ms 72 ms r2.lon-the.exa.net.uk [82.219.2.45]

12 15 ms 14 ms 15 ms lon-the-sr2.net.exa.net.uk [82.219.45.242]

13 15 ms 13 ms 13 ms lon-thn-sr2.net.exa.net.uk [82.219.45.17]

14 82.219.4.101 reports: Destination protocol unreachable.

Posted

Turns out it's fine that it does that, should have tested from Linux too

 

12 lon-thn-sr2.net.exa.net.uk (82.219.45.17) 13.978 ms 13.937 ms 13.857 ms

13 * 82.219.4.101 (82.219.4.101) 12.729 ms 12.661 ms

  • Thanks 1

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now



×
×
  • Create New...