bgpreport

Network · data from 2026-11-12

AS19210 SYNCHRONOSS - SYNCHRONOSS TECHNOLOGIES

Registry name: SYNCHRONOSS - SYNCHRONOSS TECHNOLOGIES, US · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS19210, 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.
68.170.26.0/24 No ROA None 673 100% 67
192.92.106.0/24 No ROA Other origin only 673 100% 67
68.170.23.0/24 No ROA None 672 100% 67
2620:11b:4002::/48 No ROA None 635 100% 68
2620:11b:4018::/48 No ROA None 635 100% 68
2620:11b:4000::/48 No ROA None 634 100% 68
74.116.105.0/24 Valid RIR databaseARIN 672 100% 67

AS-SET

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

  • ROA: none6
  • Route object: none6
ChangePrefix or setDetailFull-table peers
ROA: none68.170.26.0/24No ROA covers it. Add a ROA for AS19210, maxLength 24.673 of 673
Route object: none68.170.26.0/24No route object for it. Add a route object with origin AS19210 in the RIR database for the space.673 of 673
ROA: none192.92.106.0/24No ROA covers it. Add a ROA for AS19210, maxLength 24.673 of 673
Route object: none192.92.106.0/24Route objects for it name AS47870. Add a route object with origin AS19210 in the RIR database for the space.673 of 673
ROA: none68.170.23.0/24No ROA covers it. Add a ROA for AS19210, maxLength 24.672 of 673
Route object: none68.170.23.0/24No route object for it. Add a route object with origin AS19210 in the RIR database for the space.672 of 673
ROA: none2620:11b:4002::/48No ROA covers it. Add a ROA for AS19210, maxLength 48.635 of 636
Route object: none2620:11b:4002::/48No route object for it. Add a route object with origin AS19210 in the RIR database for the space.635 of 636
ROA: none2620:11b:4018::/48No ROA covers it. Add a ROA for AS19210, maxLength 48.635 of 636
Route object: none2620:11b:4018::/48No route object for it. Add a route object with origin AS19210 in the RIR database for the space.635 of 636
ROA: none2620:11b:4000::/48No ROA covers it. Add a ROA for AS19210, maxLength 48.634 of 636
Route object: none2620:11b:4000::/48No route object for it. Add a route object with origin AS19210 in the RIR database for the space.634 of 636

Route objects not announced

Every route object with origin AS19210 is announced.

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.