bgpreport

Network · data from 2026-11-12

AS263342

Not in the RIR AS name list · not in PeeringDB

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

Announced routes

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

191.36.224.0/23 Invalid: origin Other origin only 2 0%low visibility 2
191.36.226.0/23 Invalid: origin Other origin only 2 0%low visibility 2

AS-SET

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

  • ROA: origin2
  • Route object: none2
  • Route object: not announced11
ChangePrefix or setDetailFull-table peers
ROA: origin191.36.224.0/23ROAs covering it name AS263980, not AS263342. If AS263342 should announce it, add a ROA for AS263342.2 of 673
Route object: none191.36.224.0/23Route objects for it name AS263980. Add a route object with origin AS263342 in the RIR database for the space.2 of 673
ROA: origin191.36.226.0/23ROAs covering it name AS263980, not AS263342. If AS263342 should announce it, add a ROA for AS263342.2 of 673
Route object: none191.36.226.0/23Route objects for it name AS263980. Add a route object with origin AS263342 in the RIR database for the space.2 of 673

Route objects not announced

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

2804:14a8::/32RADB, TCNo ROA
2804:14a8::/33RADB, TCNo ROA
2804:14a8::/34RADBNo ROA
2804:14a8:a::/48RADBNo ROA
2804:14a8:b::/48RADBNo ROA
2804:14a8:c::/48RADBNo ROA
2804:14a8:d::/48RADBNo ROA
2804:14a8:e::/48RADBNo ROA
2804:14a8:f::/48RADBNo ROA
2804:14a8:8000::/33TCNo ROA
2804:189c::/32RADBNo 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.