bgpreport

Network · data from 2026-11-12

AS399868 SNAPCOM

Registry name: SNAPCOM - Snapcom, US · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS399868, 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.
2602:fc5c:499::/48 No ROA Other origin only 606 95% 67
23.183.48.0/24 No ROA RIR databaseARIN 673 100% 70
173.249.176.0/24 No ROA RIR databaseARIN 673 100% 70
173.249.177.0/24 No ROA RIR databaseARIN 673 100% 70
173.249.179.0/24 No ROA RIR databaseARIN 673 100% 67
2602:fc5c:3::/48 No ROA RIR databaseARIN 635 100% 67
2602:fc5c:4::/48 No ROA RIR databaseARIN 634 100% 68
2602:fc5c:1::/48 No ROA RIR databaseARIN 605 95% 67
2602:fc5c:99::/48 No ROA RIR databaseARIN 605 95% 67

AS-SET

AS399868's PeeringDB record names no 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 12 are in fix.csv.

  • ROA: none9
  • Route object: none1
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
ROA: none2602:fc5c:499::/48No ROA covers it. Add a ROA for AS399868, maxLength 48.606 of 636
Route object: none2602:fc5c:499::/48Route objects for it name AS174, AS6939. Add a route object with origin AS399868 in the RIR database for the space.606 of 636
ROA: none23.183.48.0/24No ROA covers it. Add a ROA for AS399868, maxLength 24.673 of 673
ROA: none173.249.176.0/24No ROA covers it. Add a ROA for AS399868, maxLength 24.673 of 673
ROA: none173.249.177.0/24No ROA covers it. Add a ROA for AS399868, maxLength 24.673 of 673
ROA: none173.249.179.0/24No ROA covers it. Add a ROA for AS399868, maxLength 24.673 of 673
ROA: none2602:fc5c:3::/48No ROA covers it. Add a ROA for AS399868, maxLength 48.635 of 636
ROA: none2602:fc5c:4::/48No ROA covers it. Add a ROA for AS399868, maxLength 48.634 of 636
ROA: none2602:fc5c:1::/48No ROA covers it. Add a ROA for AS399868, maxLength 48.605 of 636
ROA: none2602:fc5c:99::/48No ROA covers it. Add a ROA for AS399868, maxLength 48.605 of 636

Route objects not announced

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

173.249.178.0/24ARINNo ROA
2602:fc5c:2::/48ARINNo 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.