bgpreport

Network · data from 2026-11-12

AS397497 PAYCOM - Paycom Payroll, LLC

Registry name: PAYCOM - Paycom Payroll, LLC, US · not in PeeringDB

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

Announced routes

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

216.226.4.0/24 No ROA Other origin onlycovered by 216.226.0.0/20 673 100% 67
216.226.5.0/24 No ROA Nonecovered by 216.226.0.0/20 673 100% 67
216.226.6.0/24 No ROA Nonecovered by 216.226.0.0/20 673 100% 67
216.226.7.0/24 No ROA Nonecovered by 216.226.0.0/20 673 100% 67
2602:815:4005::/48 No ROA Nonecovered by 2602:815:4000::/44 635 100% 67
216.226.1.0/24 No ROA Other IRR onlyRADB 673 100% 67
216.226.2.0/24 No ROA Other IRR onlyRADB 673 100% 67
216.226.3.0/24 No ROA Other IRR onlyRADB 673 100% 67
216.226.0.0/24 No ROA Other IRR onlyRADB 671 100% 67
216.226.8.0/24 No ROA Other IRR onlyRADB 671 100% 67
216.226.10.0/24 No ROA Other IRR onlyRADB 671 100% 67
2602:815:4001::/48 No ROA Other IRR onlyRADB 635 100% 67
2602:815:4002::/48 No ROA Other IRR onlyRADB 635 100% 67

AS-SET

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

  • ROA: none13
  • Route object: none5
  • Route object: RIR8
  • Route object: not announced4
ChangePrefix or setDetailFull-table peers
ROA: none216.226.4.0/24No ROA covers it. Add a ROA for AS397497, maxLength 24.673 of 673
Route object: none216.226.4.0/24Route objects for it name AS22773. A route object for 216.226.0.0/20 with origin AS397497 covers it (filters allowing more-specifics accept it). Add a route object with origin AS397497 in the RIR database for the space.673 of 673
ROA: none216.226.5.0/24No ROA covers it. Add a ROA for AS397497, maxLength 24.673 of 673
Route object: none216.226.5.0/24No route object for it. A route object for 216.226.0.0/20 with origin AS397497 covers it (filters allowing more-specifics accept it). Add a route object with origin AS397497 in the RIR database for the space.673 of 673
ROA: none216.226.6.0/24No ROA covers it. Add a ROA for AS397497, maxLength 24.673 of 673
Route object: none216.226.6.0/24No route object for it. A route object for 216.226.0.0/20 with origin AS397497 covers it (filters allowing more-specifics accept it). Add a route object with origin AS397497 in the RIR database for the space.673 of 673
ROA: none216.226.7.0/24No ROA covers it. Add a ROA for AS397497, maxLength 24.673 of 673
Route object: none216.226.7.0/24No route object for it. A route object for 216.226.0.0/20 with origin AS397497 covers it (filters allowing more-specifics accept it). Add a route object with origin AS397497 in the RIR database for the space.673 of 673
ROA: none2602:815:4005::/48No ROA covers it. Add a ROA for AS397497, maxLength 48.635 of 636
Route object: none2602:815:4005::/48No route object for it. A route object for 2602:815:4000::/44 with origin AS397497 covers it (filters allowing more-specifics accept it). Add a route object with origin AS397497 in the RIR database for the space.635 of 636
ROA: none216.226.1.0/24No ROA covers it. Add a ROA for AS397497, maxLength 24.673 of 673
Route object: RIR216.226.1.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none216.226.2.0/24No ROA covers it. Add a ROA for AS397497, maxLength 24.673 of 673
Route object: RIR216.226.2.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none216.226.3.0/24No ROA covers it. Add a ROA for AS397497, maxLength 24.673 of 673
Route object: RIR216.226.3.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none216.226.0.0/24No ROA covers it. Add a ROA for AS397497, maxLength 24.671 of 673
Route object: RIR216.226.0.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none216.226.8.0/24No ROA covers it. Add a ROA for AS397497, maxLength 24.671 of 673
Route object: RIR216.226.8.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none216.226.10.0/24No ROA covers it. Add a ROA for AS397497, maxLength 24.671 of 673
Route object: RIR216.226.10.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none2602:815:4001::/48No ROA covers it. Add a ROA for AS397497, maxLength 48.635 of 636
Route object: RIR2602:815:4001::/48Route object only in RADB. Add it in the RIR database for the space.635 of 636
ROA: none2602:815:4002::/48No ROA covers it. Add a ROA for AS397497, maxLength 48.635 of 636
Route object: RIR2602:815:4002::/48Route object only in RADB. Add it in the RIR database for the space.635 of 636

Route objects not announced

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

216.226.0.0/20RADBNo ROA
2602:815:4000::/44RADBNo ROA
2602:815:4003::/48RADBNo ROA
2602:815:400d::/48RADBNo 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.