bgpreport

Network · data from 2026-11-12

AS15317 SERVEREL-AS - Serverel Inc.

Registry name: SERVEREL-AS - Serverel Inc., US · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS15317, 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.
2605:5b00::/32 No ROA RIR databaseARIN 635 100% 69
162.221.224.0/22 Valid RIR databaseARIN 673 100% 67
162.252.20.0/22 Valid RIR databaseARIN 673 100% 67
216.172.48.0/20 Valid RIR databaseARIN 673 100% 67
173.214.240.0/20 Valid RIR databaseARIN 670 100% 67
192.133.136.0/21 Valid RIR databaseARIN 670 100% 67
199.182.160.0/21 Valid RIR databaseARIN 670 100% 67

AS-SET

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

  • ROA: none1
ChangePrefix or setDetailFull-table peers
ROA: none2605:5b00::/32No ROA covers it. Add a ROA for AS15317, maxLength 32.635 of 636

Route objects not announced

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