New IP (79.135.x.x) , More services unavailable

Hi I have work new to a new IP and more services are broken, below is information on


IP Info

* ip:"79.135.101.xxx",

* city:"London",

* region:"England",

* country:"GB",

loc:"51.5085,-0.1257",
PING bbc.co.uk (151.101.0.81) 56(84) bytes of data.

--- bbc.co.uk ping statistics ---
5 packets transmitted, 0 received, 100% packet loss, time 4095ms



traceroute to bbc.co.uk (151.101.128.81), 20 hops max, 46 byte packets
 1  79.135.100.1  4.219 ms
 2  185.20.53.17  4.434 ms
 3  *
 4  *
 5  *
 6  *
 7  *
 8  *
 9  *
10  *
11  *
12  *
13  *
14  *
15  *
16  *
17  *
18  *
19  *
20  *
PING google.co.uk (216.58.204.67) 56(84) bytes of data.
64 bytes from lhr25s13-in-f3.1e100.net (216.58.204.67): icmp_seq=1 ttl=59 time=4.63 ms
64 bytes from lhr25s13-in-f3.1e100.net (216.58.204.67): icmp_seq=2 ttl=59 time=4.75 ms
64 bytes from lhr25s13-in-f3.1e100.net (216.58.204.67): icmp_seq=3 ttl=59 time=4.77 ms
64 bytes from lhr25s13-in-f3.1e100.net (216.58.204.67): icmp_seq=4 ttl=59 time=4.60 ms
64 bytes from lhr25s13-in-f3.1e100.net (216.58.204.67): icmp_seq=5 ttl=59 time=4.56 ms

--- google.co.uk ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 4007ms
rtt min/avg/max/mdev = 4.560/4.660/4.766/0.083 ms   


traceroute to google.co.uk (216.58.204.67), 20 hops max, 46 byte packets
 1  79.135.100.1  4.399 ms
 2  185.20.53.17  4.339 ms
 3  72.14.223.190  4.380 ms
 4  *
 5  142.251.52.142  4.982 ms
 6  192.178.97.168  4.661 ms
 7  142.250.215.205  11.428 ms
 8  72.14.237.52  5.473 ms
 9  192.178.97.95  5.799 ms
10  216.58.204.67  4.628 ms

I have rebooted both ONT and router with no improvement, is anyone else seeing this / is there a fix ?

I’m the same, moved onto the new 79 ip last night and only a handful of sites are working this morning. If I connect to a vpn I’m OK.

Same for me, moved to 79.135 overnight and half the net is inaccessible.

Another broken service is reddit

PING reddit.map.fastly.net (151.101.129.140) 56(84) bytes of data.

--- reddit.map.fastly.net ping statistics ---
5 packets transmitted, 0 received, 100% packet loss, time 4161ms



traceroute to www.reddit.com (151.101.1.140), 30 hops max, 46 byte packets
 1  79.135.100.1 (79.135.100.1)  4.467 ms  4.830 ms  4.579 ms
 2  yayzi-broadband.pe0.lhr0.uk.as61049.net (185.20.53.17)  4.295 ms  4.461 ms  4.443 ms
 3  *  *  *
 4  *  *  *
 5  *  *  *
Tracing route to bbc.co.uk [151.101.64.81]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  RT-AX82U-B140 [192.168.50.1]
  2     1 ms     1 ms     1 ms  192.168.0.1
  3     4 ms     3 ms     3 ms  79.135.100.1
  4     3 ms     3 ms     3 ms  yayzi-broadband.pe0.lhr0.uk.as61049.net [185.20.53.17]
  5     *        *        *     Request timed out.
  6     *        *        *     Request timed out.
  7     *        *        *     Request timed out.
  8     *        *        *     Request timed out.
  9     *        *        *     Request timed out.
 10     *        *        *     Request timed out.
 11     *        *        *     Request timed out.
 12     *        *        *     Request timed out.
 13     *        *        *     Request timed out.
 14     *        *        *     Request timed out.
 15     *        *        *     Request timed out.
 16     *        *        *     Request timed out.
 17     *        *        *     Request timed out.
 18     *        *        *     Request timed out.
 19     *        *        *     Request timed out.
 20     *        *        *     Request timed out.
 21     *        *        *     Request timed out.
 22     *        *        *     Request timed out.
 23     *        *        *     Request timed out.
 24     *        *        *     Request timed out.
 25
Tracing route to reddit.com [151.101.129.140]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  RT-AX82U-B140 [192.168.50.1]
  2     1 ms     1 ms     1 ms  192.168.0.1
  3     3 ms     3 ms     3 ms  79.135.100.1
  4     4 ms     3 ms     3 ms  yayzi-broadband.pe0.lhr0.uk.as61049.net [185.20.53.17]
  5     *        *        *     Request timed out.
  6     *        *        *     Request timed out.
  7     *        *        *     Request timed out.
  8     *        *        *     Request timed out.

I’ll add Wordle in here too (ok I know… not mission critical… but a daily distraction)

Also on the 79.135.101.xxx range

I am on the same subnet and see the same issues as you. Possibly whatever is using a CDN (ex peerCDN and Akamai CDN) is not working, quite a lot of websites. Feeling is that our subnet isn’t advertised everywhere.

1 Like

mine also on 79.135.101.xxx range and most sites arnt connecting or taking forever to load…is this a known issue do we know?

1 Like

Yes, known issue. I believe Yayzi are on it.

fast.com also unreachable :slight_smile:

PING www.fast.com (104.124.161.107) 56(84) bytes of data.

--- www.fast.com ping statistics ---
5 packets transmitted, 0 received, 100% packet loss, time 4188ms

traceroute to fast.com (104.124.161.107), 30 hops max, 46 byte packets
 1  79.135.100.1 (79.135.100.1)  4.350 ms  4.443 ms  5.040 ms
 2  yayzi-broadband.pe0.lhr0.uk.as61049.net (185.20.53.17)  5.128 ms  3.912 ms  4.447 ms
 3  *  *  *
 4  *  *  *

cheers mate…i seen the issue where people are being shown as in Iran!! They messed this up big time

We are aware of an ongoing issue where some IP addresses are incorrectly showing as being located in Iran. Our team is actively addressing this matter and collaborating closely with our GeoDB (Geolocation Database) providers to rectify the situation as quickly as possible.

Key Points:

  • The issue affects only a subset of IP addresses
  • We are in direct communication with GeoDB providers
  • A solution is being expedited to ensure accurate geolocation data

We appreciate your patience and understanding as we work to resolve this discrepancy. We will provide updates as soon as the geolocation data has been corrected.

TLDR: We are aware of the GeoDB issue and it’s being resolved

Perfection is a practiced art, not a given :grin:

I’m sure we’ve all made bad decisions, so I think the benefit of doubt is in order. I’m sure they’re kicking themselves to death already.

Yep! :confused: but it’s how we deal with it now and how quickly we resolve the issues.

1 Like

@Yayzi_Team

Looks like geo ip for the 79.135.101.xx range is fixed now showing UK for me.

However many sites I use are nor loading or partilally loading. I have rebooted the ONT this morning, flushed DNS cahse and restarted my dns servers.

just start of the day here are some …

http://reddit.com/

I suspect they may have stale GeoIP data for the new range — IR not UK.

I’m sure you’ll do it as fast as you can :+1: At least something is being done about that terrible old line, even if this one is having some teething problems.

This is not the location issue anymore

also can confirm githiub is down (no cdn content available)

PING github.githubassets.com (185.199.108.154) 56(84) bytes of data.

--- github.githubassets.com ping statistics ---
5 packets transmitted, 0 received, 100% packet loss, time 4172ms




traceroute to github.githubassets.com (185.199.110.154), 30 hops max, 46 byte packets
 1  79.135.100.1 (79.135.100.1)  4.692 ms  4.691 ms  4.384 ms
 2  yayzi-broadband.pe0.lhr0.uk.as61049.net (185.20.53.17)  4.488 ms  4.366 ms  4.073 ms
 3  *  *  *
 4  *  *  *
 5  *  *  *
 6  *  *  *
 7  *  *  *
 8  *  *  *
 9  *  *  *
10  *  *  *
11  *  *  *
12  *  *  *

Yep…all of a sudden if i try to login to twitter i cant…same as tiktok…and many searching attemtps in chrome and firefox… but i can use my phone on three data no problems… iv even just done a fresh install of windows to narrow down any doubt

Looks like its the CDN’s that are not available, see apples below

PING e2885.e9.akamaiedge.net (104.78.170.24) 56(84) bytes of data.

--- e2885.e9.akamaiedge.net ping statistics ---
5 packets transmitted, 0 received, 100% packet loss, time 4150ms



traceroute to appleid.cdn-apple.com (104.78.170.24), 30 hops max, 46 byte packets
 1  79.135.100.1 (79.135.100.1)  4.452 ms  4.586 ms  4.340 ms
 2  yayzi-broadband.pe0.lhr0.uk.as61049.net (185.20.53.17)  4.593 ms  4.165 ms  4.390 ms
 3  *  *  *
 4  *  *  *

Location is showing fine for me @Yayzi_Team

but still unable to access at least :

  • apple account
  • bbc
  • reddit
  • github
  • fast.com
1 Like