bgpreport

Network · data from 2026-11-12

AS397182 SERVICENOW-WAVE - SERVICENOW, INC.

Registry name: SERVICENOW-WAVE - SERVICENOW, INC., US · not in PeeringDB

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

Announced routes

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

2608:1c7::/48 No ROA None 635 100% 67
2608:1c7:1::/48 No ROA None 635 100% 67
148.139.128.0/22 Valid RIR databaseRIPE 673 100% 67
148.139.132.0/22 Valid RIR databaseRIPE 673 100% 67
149.96.184.0/22 Valid RIR databaseARIN 673 100% 67
149.96.188.0/22 Valid RIR databaseARIN 673 100% 67
149.96.192.0/24 Valid RIR databaseARIN 673 100% 67
149.96.193.0/24 Valid RIR databaseARIN 673 100% 67
2606:c7c0:110::/48 Valid RIR databaseARIN 636 100% 67
2606:c7c0:120::/48 Valid RIR databaseARIN 636 100% 67

AS-SET

AS397182 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 22 are in fix.csv.

  • ROA: none2
  • Route object: none2
  • Route object: not announced18
ChangePrefix or setDetailFull-table peers
ROA: none2608:1c7::/48No ROA covers it. Add a ROA for AS397182, maxLength 48.635 of 636
Route object: none2608:1c7::/48No route object for it. Add a route object with origin AS397182 in the RIR database for the space.635 of 636
ROA: none2608:1c7:1::/48No ROA covers it. Add a ROA for AS397182, maxLength 48.635 of 636
Route object: none2608:1c7:1::/48No route object for it. Add a route object with origin AS397182 in the RIR database for the space.635 of 636

Route objects not announced

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

148.139.128.0/24RIPEValid
148.139.129.0/24RIPEValid
148.139.130.0/24RIPEValid
148.139.131.0/24RIPEValid
148.139.132.0/24RIPEValid
148.139.133.0/24RIPEValid
148.139.134.0/24RIPEValid
148.139.135.0/24RIPEValid
149.96.192.0/26ARINValid
149.96.192.64/26ARINValid
149.96.192.128/26ARINValid
149.96.192.192/26ARINValid
149.96.193.0/26ARINValid
149.96.193.64/26ARINValid
149.96.193.128/26ARINValid
149.96.193.192/26ARINValid
2406:9f01::/32APNICValid
2606:c7c0::/32ARINValid

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.