IP assigned has a bad reputaiton 79.135.***.**

My IP is 65 as well

1 Like

Same here with Ticketmaster

1 Like

Get it sorted, every database except the one above shows no issues. We’re already on it with IPQualityScore.

Thanks!

Mine just went worse. rising up to 93 now… Great!

So I wouldn’t go by just the free lookup on IPQualityScore - mine is now showing as 99 :open_mouth:

I then went and created a free account and it’s coming up as 0 now, all good - but the free lookup still says 99. A lot of dark pattern in that designed to get business methinks.

However, this still hasn’t resolved TicketMaster and Reddit for me. They’re both obviously using some database that still says the 79.135.x.x range is bad - perhaps @Yayzi_Team you’d be better off trying to find out what database that is?

And also for those of us that aren’t day to day networking professionals - do these reputations get better after a period of time, or are they marked as bad until someone ā€˜sorts it’?

Do we need a router reboot?

Ticketmaster still unavailable… Disney no go

Same on 185…

I suspect that website isn’t showing the correct info, we’re looking into it.

This doesn’t help any of you on the receiving end of a bad reputation score, but… IP reputation is about as accurate a science as finding water with a bent coathanger (actually, it’s probably worse)… many domestic IPs fall foul of the fact that many domestic devices end up riddled with malware (IoT devices, I’m looking at you) and part of a botnet… although for so many addresses to be blacklisted in a range is strange (unless the range was previously owned by OVH … sorry, industry joke I imagine!).

The way it gets fixed is usually this:

Customer complains to either the service provider (Yayzi) or service they’re trying to access (say, Disney)
Service owner reaches out to their IPrep provider and asks them to fix the score because their customers are angry
IPrep provider fixes the score after ignoring the ticket for an indeterminate amount of time
IPrep database is updated
Indeterminate amount of time passes before whatever device exposes that service downloads the updated DB

It’s a shame everyone hid their IP address here or I’d have looked them up here - URL/IP Lookup | Webroot BrightCloud - Brightcloud are a fairly reputable (pardon the pun) reputation service provider; it’s who we resell at $work (and $work devices front Disney, Ticketmaster, and many others … with the exception of Netflix, because they rolled their own proxy infrastructure)

Still weird that range has so many bad apples in it, though!

1 Like

Im getting CAPTCHAs a lot today after the move. Me thinks IPXO wasn’t very good at managing the ranges with whoever had them last.

1 Like

We’re going to pull the 74.x addresses overnight. Clearly they are bad. We’ll move everyone to our 149.X addresses.

2 Likes

Oh god please change this 75 ip address my kids are going ASD crazy… roblox doesnt work not most of the online ga.es they play.
I have no hair ao im going to pull off my scalp. But im all honesty my download speeds on this IP have nose dived from 1400 wireless to under 200.

It will be changed

Oh ffs. I just sorted the Disney… :joy::joy::joy::joy::joy:

Sorry! :frowning: we’ve made the decision for everyone so you can get on Ticketmaster… :sweat_smile:

I am on the 79.135. When is the swap due to be done?

Hi

I am also on the 79.135.X, will this be changing overnight?

Can you issue me with a good IP address so I can go manual and not have DHCP on my WAN port and alway then have the correct address?

Finding hard to come up with a good excuses on why my kids cant watch Disney anymore…

1 Like

See pinned post :slight_smile:

1 Like

I have just remembered that I have an Express VPN account, so I have used openvpn via the express-vpn servers in Docklands and I have got disney+ working and got the kids off my back…

Just incase anyone has an Express VPN account and a Asus router I have just set-up a VPN from my router to Docklands in London, and I am still getting a 1816Mbps encrypted connection, so really pleased with that speed.

2 Likes

I’m seeing the same issues on 79.135.xxx.xxx IP - are you moving customers from this range too? I cannot get on Reddit at all.

I’m also seeing packet loss - is that known about already too?