bgpreport

Network · data from 2026-11-12

AS29967 ARAMARK-NS - Aramark Services, Inc.

Registry name: ARAMARK-NS - Aramark Services, Inc., US · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS29967, 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.
161.195.120.0/24 Valid Nonecovered by 161.195.120.0/22 673 100% 67
161.195.121.0/24 Valid Nonecovered by 161.195.120.0/22 673 100% 67
161.195.122.0/24 Valid Nonecovered by 161.195.120.0/22 673 100% 67
161.195.123.0/24 Valid Nonecovered by 161.195.120.0/22 673 100% 67
161.195.73.0/24 Valid RIR databaseARIN 673 100% 67
161.195.65.0/24 Valid RIR databaseARIN 672 100% 67
161.195.66.0/24 Valid RIR databaseARIN 672 100% 67
161.195.68.0/24 Valid RIR databaseARIN 672 100% 67
161.195.70.0/24 Valid RIR databaseARIN 672 100% 67
161.195.176.0/24 Valid RIR databaseARIN 672 100% 67
161.195.177.0/24 Valid RIR databaseARIN 672 100% 67

AS-SET

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

  • Route object: none4
  • Route object: not announced3
ChangePrefix or setDetailFull-table peers
Route object: none161.195.120.0/24No route object for it. A route object for 161.195.120.0/22 with origin AS29967 covers it (filters allowing more-specifics accept it). Add a route object with origin AS29967 in the RIR database for the space.673 of 673
Route object: none161.195.121.0/24No route object for it. A route object for 161.195.120.0/22 with origin AS29967 covers it (filters allowing more-specifics accept it). Add a route object with origin AS29967 in the RIR database for the space.673 of 673
Route object: none161.195.122.0/24No route object for it. A route object for 161.195.120.0/22 with origin AS29967 covers it (filters allowing more-specifics accept it). Add a route object with origin AS29967 in the RIR database for the space.673 of 673
Route object: none161.195.123.0/24No route object for it. A route object for 161.195.120.0/22 with origin AS29967 covers it (filters allowing more-specifics accept it). Add a route object with origin AS29967 in the RIR database for the space.673 of 673

Route objects not announced

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

161.195.120.0/22ARINValid
161.195.139.0/24ARINValid
161.195.194.0/24ARINValid

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.