bgpreport

Network · data from 2026-11-12

AS7363

Not in the RIR AS name list · not in PeeringDB

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

Announced routes

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

199.233.245.0/24 No ROA Nonecovered by 199.233.244.0/22 673 100% 67
199.233.246.0/24 No ROA Nonecovered by 199.233.244.0/22 673 100% 67
199.233.247.0/24 No ROA Nonecovered by 199.233.244.0/22 673 100% 67
199.233.244.0/24 No ROA Nonecovered by 199.233.244.0/22 671 100% 67
199.233.244.0/22 No ROA RIR databaseALTDB, ARIN 1 0%low visibility 1

AS-SET

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

  • ROA: none5
  • Route object: none4
  • Route object: not announced4
ChangePrefix or setDetailFull-table peers
ROA: none199.233.245.0/24No ROA covers it. Add a ROA for AS7363, maxLength 24.673 of 673
Route object: none199.233.245.0/24No route object for it. A route object for 199.233.244.0/22 with origin AS7363 covers it (filters allowing more-specifics accept it). Add a route object with origin AS7363 in the RIR database for the space.673 of 673
ROA: none199.233.246.0/24No ROA covers it. Add a ROA for AS7363, maxLength 24.673 of 673
Route object: none199.233.246.0/24No route object for it. A route object for 199.233.244.0/22 with origin AS7363 covers it (filters allowing more-specifics accept it). Add a route object with origin AS7363 in the RIR database for the space.673 of 673
ROA: none199.233.247.0/24No ROA covers it. Add a ROA for AS7363, maxLength 24.673 of 673
Route object: none199.233.247.0/24No route object for it. A route object for 199.233.244.0/22 with origin AS7363 covers it (filters allowing more-specifics accept it). Add a route object with origin AS7363 in the RIR database for the space.673 of 673
ROA: none199.233.244.0/24No ROA covers it. Add a ROA for AS7363, maxLength 24.671 of 673
Route object: none199.233.244.0/24No route object for it. A route object for 199.233.244.0/22 with origin AS7363 covers it (filters allowing more-specifics accept it). Add a route object with origin AS7363 in the RIR database for the space.671 of 673
ROA: none199.233.244.0/22No ROA covers it. Add a ROA for AS7363, maxLength 22.1 of 673

Route objects not announced

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

62.19.244.0/22ALTDBNo ROA
208.93.118.0/23ALTDBNo ROA
2403:c880::/31ALTDBNo ROA
2605:980::/32ALTDB, ARIN, RADBNo 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.