bgpreport

Network · data from 2026-11-12

AS5787 SNAPONSBS - Snap-on Business Solutions Inc.

Registry name: SNAPONSBS - Snap-on Business Solutions Inc., US · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS5787, 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.
199.255.36.0/24 No ROA Nonecovered by 199.255.36.0/22 672 100% 67
199.255.37.0/24 No ROA Nonecovered by 199.255.36.0/22 672 100% 67
199.255.38.0/24 No ROA Nonecovered by 199.255.36.0/22 672 100% 67
199.255.39.0/24 No ROA Nonecovered by 199.255.36.0/22 672 100% 67
2620:83::/48 No ROA Other IRR onlyRADB 634 100% 69
74.219.168.0/24 Valid RIR databaseARIN 672 100% 67
74.219.169.0/24 Valid RIR databaseARIN 672 100% 67
74.219.170.0/24 Valid RIR databaseARIN 672 100% 67
74.219.171.0/24 Valid RIR databaseARIN 672 100% 67

AS-SET

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

  • ROA: none5
  • Route object: none4
  • Route object: RIR1
  • Route object: not announced4
ChangePrefix or setDetailFull-table peers
ROA: none199.255.36.0/24No ROA covers it. Add a ROA for AS5787, maxLength 24.672 of 673
Route object: none199.255.36.0/24No route object for it. A route object for 199.255.36.0/22 with origin AS5787 covers it (filters allowing more-specifics accept it). Add a route object with origin AS5787 in the RIR database for the space.672 of 673
ROA: none199.255.37.0/24No ROA covers it. Add a ROA for AS5787, maxLength 24.672 of 673
Route object: none199.255.37.0/24No route object for it. A route object for 199.255.36.0/22 with origin AS5787 covers it (filters allowing more-specifics accept it). Add a route object with origin AS5787 in the RIR database for the space.672 of 673
ROA: none199.255.38.0/24No ROA covers it. Add a ROA for AS5787, maxLength 24.672 of 673
Route object: none199.255.38.0/24No route object for it. A route object for 199.255.36.0/22 with origin AS5787 covers it (filters allowing more-specifics accept it). Add a route object with origin AS5787 in the RIR database for the space.672 of 673
ROA: none199.255.39.0/24No ROA covers it. Add a ROA for AS5787, maxLength 24.672 of 673
Route object: none199.255.39.0/24No route object for it. A route object for 199.255.36.0/22 with origin AS5787 covers it (filters allowing more-specifics accept it). Add a route object with origin AS5787 in the RIR database for the space.672 of 673
ROA: none2620:83::/48No ROA covers it. Add a ROA for AS5787, maxLength 48.634 of 636
Route object: RIR2620:83::/48Route object only in RADB. Add it in the RIR database for the space.634 of 636

Route objects not announced

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

74.219.168.0/22ARIN, RADBValid
74.219.168.0/23ARINValid
74.219.170.0/23ARINValid
199.255.36.0/22RADBNo 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.