bgpreport

Network · data from 2026-11-12

AS213990 AOFB

Registry name: AOFB AOFB Telecom Networks Ltd, GB · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS213990, 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.
143.20.252.0/24 Invalid: origin Other origin only 4 1%low visibility 3
151.247.12.0/24 Invalid: origin Other origin only 4 1%low visibility 3
107.158.114.0/24 Invalid: origin Other origin only 2 0%low visibility 2
66.6.58.0/24 No ROA None 2 0%low visibility 2
23.26.143.0/24 Valid Other IRR onlyRADB 668 99% 67
31.59.69.0/24 Valid RIR databaseRADB, RIPE 668 99% 67
37.140.247.0/24 Valid RIR databaseRIPE 668 99% 67
168.222.107.0/24 Valid RIR databaseRADB, RIPE 668 99% 67
187.7.199.0/24 Valid RIR databaseRIPE 668 99% 67
191.217.165.0/24 Valid RIR databaseRIPE 668 99% 67
195.216.182.0/24 Valid RIR databaseRIPE 668 99% 67
198.175.169.0/24 Valid RIR databaseARIN, RADB 668 99% 67
45.42.43.0/24 Valid RIR databaseARIN, RADB 667 99% 67

AS-SET

AS213990'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 13 are in fix.csv.

  • ROA: origin3
  • ROA: none1
  • Route object: none4
  • Route object: RIR1
  • Route object: not announced4
ChangePrefix or setDetailFull-table peers
ROA: origin143.20.252.0/24ROAs covering it name AS834, not AS213990. If AS213990 should announce it, add a ROA for AS213990.4 of 673
Route object: none143.20.252.0/24Route objects for it name AS834. Add a route object with origin AS213990 in the RIR database for the space.4 of 673
ROA: origin151.247.12.0/24ROAs covering it name AS834, not AS213990. If AS213990 should announce it, add a ROA for AS213990.4 of 673
Route object: none151.247.12.0/24Route objects for it name AS834. Add a route object with origin AS213990 in the RIR database for the space.4 of 673
ROA: origin107.158.114.0/24ROAs covering it name AS834, not AS213990. If AS213990 should announce it, add a ROA for AS213990.2 of 673
Route object: none107.158.114.0/24Route objects for it name AS834. Add a route object with origin AS213990 in the RIR database for the space.2 of 673
ROA: none66.6.58.0/24No ROA covers it. Add a ROA for AS213990, maxLength 24.2 of 673
Route object: none66.6.58.0/24No route object for it. Add a route object with origin AS213990 in the RIR database for the space.2 of 673
Route object: RIR23.26.143.0/24Route object only in RADB. Add it in the RIR database for the space.668 of 673

Route objects not announced

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

185.100.121.0/24RADBNo ROA
185.100.122.0/24RADBNo ROA
185.100.123.0/24RADBNo ROA
2a0c:9a40:8630::/48RIPEValid

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.