bgpreport

Network · data from 2026-11-12

AS134536 ATT-NBE-GB - ATT NBE Equinix London

Registry name: ATT-NBE-GB - ATT NBE Equinix London, GB · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS134536, 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.
80.85.71.56/29 Invalid: origin None 1 0%low visibility 1
185.2.164.168/29 Invalid: origin None 1 0%low visibility 1
213.52.132.80/28 Invalid: origin None 1 0%low visibility 1
32.39.68.0/24 No ROA None 673 100% 67
194.69.169.0/24 No ROA Other IRR onlyRADB 673 100% 67
194.69.173.0/24 No ROA Other IRR onlyRADB 673 100% 67
194.69.178.0/24 No ROA Other IRR onlyRADB 673 100% 67

AS-SET

AS134536 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 14 are in fix.csv.

  • ROA: origin3
  • ROA: none4
  • Route object: none4
  • Route object: RIR3
ChangePrefix or setDetailFull-table peers
ROA: origin80.85.71.56/29ROAs covering it name AS15830, not AS134536. If AS134536 should announce it, add a ROA for AS134536.1 of 673
Route object: none80.85.71.56/29No route object for it. Add a route object with origin AS134536 in the RIR database for the space.1 of 673
ROA: origin185.2.164.168/29ROAs covering it name AS15830, AS21371, not AS134536. If AS134536 should announce it, add a ROA for AS134536.1 of 673
Route object: none185.2.164.168/29No route object for it. Add a route object with origin AS134536 in the RIR database for the space.1 of 673
ROA: origin213.52.132.80/28ROAs covering it name AS15830, not AS134536. If AS134536 should announce it, add a ROA for AS134536.1 of 673
Route object: none213.52.132.80/28No route object for it. Add a route object with origin AS134536 in the RIR database for the space.1 of 673
ROA: none32.39.68.0/24No ROA covers it. Add a ROA for AS134536, maxLength 24.673 of 673
Route object: none32.39.68.0/24No route object for it. Add a route object with origin AS134536 in the RIR database for the space.673 of 673
ROA: none194.69.169.0/24No ROA covers it. Add a ROA for AS134536, maxLength 24.673 of 673
Route object: RIR194.69.169.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none194.69.173.0/24No ROA covers it. Add a ROA for AS134536, maxLength 24.673 of 673
Route object: RIR194.69.173.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none194.69.178.0/24No ROA covers it. Add a ROA for AS134536, maxLength 24.673 of 673
Route object: RIR194.69.178.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673

Route objects not announced

Every route object with origin AS134536 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.