bgpreport

Network · data from 2026-11-12

AS8622 ISIONUK TEAM BLUE INTERNET SERVICES UK LIMITED

Registry name: ISIONUK TEAM BLUE INTERNET SERVICES UK LIMITED, GB · not in PeeringDB

5IPv4 routes 0.0% RPKI valid · 100.0% with a route object
1IPv6 routes 0.0% RPKI valid · 100.0% with a route object
0RPKI invalid 0 origin · 0 maxLength
6No ROA 0 with no route object for this origin
0Low visibility seen by under 10% of full-table peers
0Route objects not announced registered with origin AS8622, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS8622, things to look at first. Visibility = full-table peers that see it, of 673 (IPv4) and 636 (IPv6) on 75 collectors. Also as routes.csv.
85.233.160.0/19 No ROA RIR databaseRIPE 673 100% 67
94.126.40.0/24 No ROA RIR databaseRIPE 673 100% 67
195.7.224.0/19 No ROA RIR databaseRIPE 673 100% 67
212.84.96.0/19 No ROA RIR databaseRIPE 673 100% 67
213.246.64.0/18 No ROA RIR databaseRIPE 673 100% 67
2a00:13b0::/32 No ROA RIR databaseRIPE 633 100% 68

AS-SET

AS8622 isn't in PeeringDB, where networks name their AS-SET.

Fix list

The changes that would bring RPKI, the IRR and what's announced into line. Some are deliberate (a route object kept for a backup route, say); the network decides. All 6 are in fix.csv.

  • ROA: none6
ChangePrefix or setDetailFull-table peers
ROA: none85.233.160.0/19No ROA covers it. Add a ROA for AS8622, maxLength 19.673 of 673
ROA: none94.126.40.0/24No ROA covers it. Add a ROA for AS8622, maxLength 24.673 of 673
ROA: none195.7.224.0/19No ROA covers it. Add a ROA for AS8622, maxLength 19.673 of 673
ROA: none212.84.96.0/19No ROA covers it. Add a ROA for AS8622, maxLength 19.673 of 673
ROA: none213.246.64.0/18No ROA covers it. Add a ROA for AS8622, maxLength 18.673 of 673
ROA: none2a00:13b0::/32No ROA covers it. Add a ROA for AS8622, maxLength 32.633 of 636

Route objects not announced

Every route object with origin AS8622 is announced.

Routes: the 08:00 UTC snapshots of 2026-11-12 from 75 RIPE RIS and RouteViews collectors. RPKI: our rpki-client run before the snapshot. IRR: the day's dumps of the five RIR databases and RADB's mirrors. The LEVEL3 and IDNIC databases publish no dump and aren't read, so route objects only there count as none.