bgpreport

Network · data from 2026-11-12

AS198220 GoGrid Rackspace Ltd.

Registry name: GoGrid Rackspace Ltd., GB · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS198220, 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.

164.40.128.0/19 No ROA Other IRR onlyRADB 672 100% 67
173.1.184.0/21 No ROA Other IRR onlyRADB 672 100% 67

AS-SET

AS198220 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 11 are in fix.csv.

  • ROA: none2
  • Route object: RIR2
  • Route object: not announced7
ChangePrefix or setDetailFull-table peers
ROA: none164.40.128.0/19No ROA covers it. Add a ROA for AS198220, maxLength 19.672 of 673
Route object: RIR164.40.128.0/19Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none173.1.184.0/21No ROA covers it. Add a ROA for AS198220, maxLength 21.672 of 673
Route object: RIR173.1.184.0/21Route object only in RADB. Add it in the RIR database for the space.672 of 673

Route objects not announced

Route objects with origin AS198220 whose prefix no peer sees AS198220 announce. Many are kept on purpose (backup routes, space announced only in some places).

69.72.32.0/20RADBNo ROA
143.55.224.0/20RADBNo ROA
173.1.191.0/24RADBNo ROA
198.244.48.0/20RADBNo ROA
204.220.160.0/20RADBNo ROA
216.71.96.0/22RADBNo ROA
2a00:1a49::/32RADBNo ROA

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.