bgpreport

Network · data from 2026-11-12

AS5482 AllPoints Fibre Networks

Registry name: AS5482 AllPoints Fibre Limited, GB · PeeringDB

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

Announced routes

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

62.64.152.0/23 Valid None 673 100% 67
62.64.154.0/23 Valid None 673 100% 67
188.74.70.0/23 Valid None 673 100% 67
188.74.72.0/23 Valid None 673 100% 67
188.74.74.0/23 Valid None 673 100% 67
188.74.76.0/23 Valid None 673 100% 67
2a05:87c3:1000::/36 Valid None 635 100% 68
2a05:87c3:2000::/36 Valid None 635 100% 68
2a05:87c3:7000::/36 Valid None 635 100% 68
2a05:87c3:8000::/36 Valid None 635 100% 68
2a05:87c5:1000::/36 Valid None 635 100% 68
2a05:87c5:2000::/36 Valid None 635 100% 68
2a05:87c7:1000::/36 Valid None 635 100% 68
2a05:87c7:2000::/36 Valid None 635 100% 68
2a05:87c7:7000::/36 Valid None 635 100% 68
2a05:87c7:8000::/36 Valid None 635 100% 68
2a0a:5583::/32 Valid None 635 100% 68
2a0b:5f04:4000::/39 Valid Nonecovered by 2a0b:5f00::/29 635 100% 68
2a0b:5f04:5000::/39 Valid Nonecovered by 2a0b:5f00::/29 635 100% 68
51.179.192.0/18 Valid RIR databaseRIPE 673 100% 67
51.179.192.0/21 Valid RIR databaseRIPE 673 100% 67
51.179.200.0/21 Valid RIR databaseRIPE 673 100% 67
51.179.208.0/21 Valid RIR databaseRIPE 673 100% 67
141.195.128.0/19 Valid RIR databaseRIPE 673 100% 67
141.195.136.0/21 Valid RIR databaseRIPE 673 100% 67
141.195.144.0/21 Valid RIR databaseRIPE 673 100% 67
141.195.152.0/21 Valid RIR databaseRIPE 673 100% 67
217.142.64.0/18 Valid RIR databaseRIPE 673 100% 67
2a0b:5f04::/39 Valid RIR databaseRIPE 635 100% 68
2a0b:5f04:1000::/39 Valid RIR databaseRIPE 635 100% 68
2a0b:5f00::/29 Valid RIR databaseRIPE 634 100% 68

AS-SET

PeeringDB's irr_as_set for AS5482: RIPE::AS5482:AS-ORIGIN. Expanded from the day's IRR dumps the way bgpq4 does against whois.radb.net: a name with a database is read from that database only, one without from the first database in RADB's order. "Not covered" = this network's own routes that a filter built from the set would leave out (AS5482 isn't in the set, or no route object for AS5482 covers the route; more-specifics of a route object are accepted down to /24 and /48, as with bgpq4 -A -R 24 / -R 48). Customers' routes aren't counted: the collectors show each route's origin, not which network it came through.

NameDatabaseASNsSets Route objectsAS5482 in itNot covered
RIPE::AS5482:AS-ORIGIN RIPE 4141 Yes 17

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

  • Route object: none19
ChangePrefix or setDetailFull-table peers
Route object: none62.64.152.0/23No route object for it. Add a route object with origin AS5482 in the RIR database for the space.673 of 673
Route object: none62.64.154.0/23No route object for it. Add a route object with origin AS5482 in the RIR database for the space.673 of 673
Route object: none188.74.70.0/23No route object for it. Add a route object with origin AS5482 in the RIR database for the space.673 of 673
Route object: none188.74.72.0/23No route object for it. Add a route object with origin AS5482 in the RIR database for the space.673 of 673
Route object: none188.74.74.0/23No route object for it. Add a route object with origin AS5482 in the RIR database for the space.673 of 673
Route object: none188.74.76.0/23No route object for it. Add a route object with origin AS5482 in the RIR database for the space.673 of 673
Route object: none2a05:87c3:1000::/36No route object for it. Add a route object with origin AS5482 in the RIR database for the space.635 of 636
Route object: none2a05:87c3:2000::/36No route object for it. Add a route object with origin AS5482 in the RIR database for the space.635 of 636
Route object: none2a05:87c3:7000::/36No route object for it. Add a route object with origin AS5482 in the RIR database for the space.635 of 636
Route object: none2a05:87c3:8000::/36No route object for it. Add a route object with origin AS5482 in the RIR database for the space.635 of 636
Route object: none2a05:87c5:1000::/36No route object for it. Add a route object with origin AS5482 in the RIR database for the space.635 of 636
Route object: none2a05:87c5:2000::/36No route object for it. Add a route object with origin AS5482 in the RIR database for the space.635 of 636
Route object: none2a05:87c7:1000::/36No route object for it. Add a route object with origin AS5482 in the RIR database for the space.635 of 636
Route object: none2a05:87c7:2000::/36No route object for it. Add a route object with origin AS5482 in the RIR database for the space.635 of 636
Route object: none2a05:87c7:7000::/36No route object for it. Add a route object with origin AS5482 in the RIR database for the space.635 of 636
Route object: none2a05:87c7:8000::/36No route object for it. Add a route object with origin AS5482 in the RIR database for the space.635 of 636
Route object: none2a0a:5583::/32No route object for it. Add a route object with origin AS5482 in the RIR database for the space.635 of 636
Route object: none2a0b:5f04:4000::/39No route object for it. A route object for 2a0b:5f00::/29 with origin AS5482 covers it (filters allowing more-specifics accept it). Add a route object with origin AS5482 in the RIR database for the space.635 of 636
Route object: none2a0b:5f04:5000::/39No route object for it. A route object for 2a0b:5f00::/29 with origin AS5482 covers it (filters allowing more-specifics accept it). Add a route object with origin AS5482 in the RIR database for the space.635 of 636

Route objects not announced

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