bgpreport

Network · data from 2026-11-12

AS208699 ParsnsNetwork Leo Shum

Registry name: ParsnsNetwork Leo Shum, GB · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS208699, 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.
2a0e:b107:9fe::/48 No ROA RIR databaseRIPE 1 0%low visibility 1
2a06:9f81:5506::/47 Valid Nonecovered by 2a06:9f81:5500::/40 634 100% 69
2a0e:97c0:738::/48 Valid Nonecovered by 2a0e:97c0:730::/44 634 100% 69
2a0e:97c0:73a::/47 Valid Nonecovered by 2a0e:97c0:730::/44 634 100% 69
2a06:9f81:5502::/47 Valid Nonecovered by 2a06:9f81:5500::/40 2 0%low visibility 1
2a0e:97c0:730::/48 Valid Nonecovered by 2a0e:97c0:730::/44 1 0%low visibility 1
2a0e:97c0:738::/45 Valid Nonecovered by 2a0e:97c0:730::/44 1 0%low visibility 1
2602:f992:f4::/48 Valid RIR databaseARIN 634 100% 69
2a06:9f81:5508::/47 Valid RIR databaseRIPE 633 100% 69

AS-SET

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

  • ROA: none1
  • Route object: none6
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
ROA: none2a0e:b107:9fe::/48No ROA covers it. Add a ROA for AS208699, maxLength 48.1 of 636
Route object: none2a06:9f81:5506::/47No route object for it. A route object for 2a06:9f81:5500::/40 with origin AS208699 covers it (filters allowing more-specifics accept it). Add a route object with origin AS208699 in the RIR database for the space.634 of 636
Route object: none2a0e:97c0:738::/48No route object for it. A route object for 2a0e:97c0:730::/44 with origin AS208699 covers it (filters allowing more-specifics accept it). Add a route object with origin AS208699 in the RIR database for the space.634 of 636
Route object: none2a0e:97c0:73a::/47No route object for it. A route object for 2a0e:97c0:730::/44 with origin AS208699 covers it (filters allowing more-specifics accept it). Add a route object with origin AS208699 in the RIR database for the space.634 of 636
Route object: none2a06:9f81:5502::/47No route object for it. A route object for 2a06:9f81:5500::/40 with origin AS208699 covers it (filters allowing more-specifics accept it). Add a route object with origin AS208699 in the RIR database for the space.2 of 636
Route object: none2a0e:97c0:730::/48No route object for it. A route object for 2a0e:97c0:730::/44 with origin AS208699 covers it (filters allowing more-specifics accept it). Add a route object with origin AS208699 in the RIR database for the space.1 of 636
Route object: none2a0e:97c0:738::/45No route object for it. A route object for 2a0e:97c0:730::/44 with origin AS208699 covers it (filters allowing more-specifics accept it). Add a route object with origin AS208699 in the RIR database for the space.1 of 636

Route objects not announced

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

2a06:9f81:5500::/40RIPEValid
2a0e:97c0:730::/44RIPENo 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.