bgpreport

Network · data from 2026-11-12

AS153786 SERVERSTEP-AS-AP - SERVERSTEP

Registry name: SERVERSTEP-AS-AP - SERVERSTEP, IN · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS153786, 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.
163.5.209.0/24 Invalid: origin Other origin only 2 0%low visibility 2
192.231.16.0/24 Invalid: origin Other origin only 2 0%low visibility 2
213.130.140.0/24 Valid Other IRR onlyRADB 670 100% 68
27.98.206.0/24 Valid RIR databaseAPNIC 671 100% 67
27.98.207.0/24 Valid RIR databaseAPNIC 671 100% 67
103.49.129.0/24 Valid RIR databaseRADB, RIPE 670 100% 68
103.148.205.0/24 Valid RIR databaseAPNIC 670 100% 68
103.151.44.0/24 Valid RIR databaseAPNIC, RADB 670 100% 68
103.183.232.0/24 Valid RIR databaseAPNIC 670 100% 68
103.218.180.0/24 Valid RIR databaseAPNIC 670 100% 68
151.158.245.0/24 Valid RIR databaseAPNIC 670 100% 68
160.236.83.0/24 Valid RIR databaseAPNIC 670 100% 68
162.4.147.0/24 Valid RIR databaseAPNIC 670 100% 68
178.83.86.0/24 Valid RIR databaseRADB, RIPE 670 100% 68
192.232.56.0/24 Valid RIR databaseAPNIC 670 100% 68
162.141.153.0/24 Valid RIR databaseRADB, RIPE 663 99% 68
103.88.59.0/24 Valid RIR databaseAPNIC 2 0%low visibility 2
2401:e920:8800::/48 Valid RIR databaseAPNIC 1 0%low visibility 1

AS-SET

AS153786 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 6 are in fix.csv.

  • ROA: origin2
  • Route object: none2
  • Route object: RIR1
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: origin163.5.209.0/24ROAs covering it name AS218568, not AS153786. If AS153786 should announce it, add a ROA for AS153786.2 of 673
Route object: none163.5.209.0/24Route objects for it name AS218568. Add a route object with origin AS153786 in the RIR database for the space.2 of 673
ROA: origin192.231.16.0/24ROAs covering it name AS140133, not AS153786. If AS153786 should announce it, add a ROA for AS153786.2 of 673
Route object: none192.231.16.0/24Route objects for it name AS140133. Add a route object with origin AS153786 in the RIR database for the space.2 of 673
Route object: RIR213.130.140.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673

Route objects not announced

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

198.195.247.0/24ALTDBNo 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.