bgpreport

Network · data from 2026-11-12

AS61180 A2B IP

Registry name: A2B2 A2B IP B.V., NL · PeeringDB

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

Announced routes

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

2a12:4180:42::/48 Invalid: origin None 1 0%low visibility 1
2a12:4180:42:1::/64 Invalid: origin None 1 0%low visibility 1
2a12:4180:42:2::/64 Invalid: origin None 1 0%low visibility 1
2a06:2602:3::/48 Valid None 4 1%low visibility 3
2a06:2602:4::/48 Valid None 4 1%low visibility 3
2a06:2602:1d::/48 Valid None 4 1%low visibility 3
2a06:2602:43::/48 Valid None 4 1%low visibility 3
2a06:2602:7c::/48 Valid None 4 1%low visibility 3
2a06:2602:83::/48 Valid None 4 1%low visibility 3
2a06:2602:84::/48 Valid None 4 1%low visibility 3
2a06:2602:86::/48 Valid None 4 1%low visibility 3
2a06:2602:89::/48 Valid None 4 1%low visibility 3

AS-SET

AS61180's PeeringDB record names no 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 15 are in fix.csv.

  • ROA: origin3
  • Route object: none12
ChangePrefix or setDetailFull-table peers
ROA: origin2a12:4180:42::/48ROAs covering it name AS51088, not AS61180. If AS61180 should announce it, add a ROA for AS61180.1 of 636
Route object: none2a12:4180:42::/48No route object for it. Add a route object with origin AS61180 in the RIR database for the space.1 of 636
ROA: origin2a12:4180:42:1::/64ROAs covering it name AS51088, not AS61180. If AS61180 should announce it, add a ROA for AS61180.1 of 636
Route object: none2a12:4180:42:1::/64No route object for it. Add a route object with origin AS61180 in the RIR database for the space.1 of 636
ROA: origin2a12:4180:42:2::/64ROAs covering it name AS51088, not AS61180. If AS61180 should announce it, add a ROA for AS61180.1 of 636
Route object: none2a12:4180:42:2::/64No route object for it. Add a route object with origin AS61180 in the RIR database for the space.1 of 636
Route object: none2a06:2602:3::/48No route object for it. Add a route object with origin AS61180 in the RIR database for the space.4 of 636
Route object: none2a06:2602:4::/48No route object for it. Add a route object with origin AS61180 in the RIR database for the space.4 of 636
Route object: none2a06:2602:1d::/48No route object for it. Add a route object with origin AS61180 in the RIR database for the space.4 of 636
Route object: none2a06:2602:43::/48No route object for it. Add a route object with origin AS61180 in the RIR database for the space.4 of 636
Route object: none2a06:2602:7c::/48No route object for it. Add a route object with origin AS61180 in the RIR database for the space.4 of 636
Route object: none2a06:2602:83::/48No route object for it. Add a route object with origin AS61180 in the RIR database for the space.4 of 636
Route object: none2a06:2602:84::/48No route object for it. Add a route object with origin AS61180 in the RIR database for the space.4 of 636
Route object: none2a06:2602:86::/48No route object for it. Add a route object with origin AS61180 in the RIR database for the space.4 of 636
Route object: none2a06:2602:89::/48No route object for it. Add a route object with origin AS61180 in the RIR database for the space.4 of 636

Route objects not announced

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