bgpreport

Network · data from 2026-11-12

AS274879 AS274879 - DYNAMIC NETWORKS SOLUTIONS SAS ZOMAC

Registry name: AS274879 - DYNAMIC NETWORKS SOLUTIONS SAS ZOMAC, CO · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS274879, 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.
2803:7a30::/41 Valid Nonecovered by 2803:7a30::/33 619 97% 67
2803:7a30:100::/41 Valid Nonecovered by 2803:7a30::/33 619 97% 67
45.194.7.0/24 Valid Other IRR onlyRADB 669 99% 67

AS-SET

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

  • Route object: none2
  • Route object: RIR1
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
Route object: none2803:7a30::/41No route object for it. A route object for 2803:7a30::/33 with origin AS274879 covers it (filters allowing more-specifics accept it). Add a route object with origin AS274879 in the RIR database for the space.619 of 636
Route object: none2803:7a30:100::/41No route object for it. A route object for 2803:7a30::/33 with origin AS274879 covers it (filters allowing more-specifics accept it). Add a route object with origin AS274879 in the RIR database for the space.619 of 636
Route object: RIR45.194.7.0/24Route object only in RADB. Add it in the RIR database for the space.669 of 673

Route objects not announced

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

2803:7a30::/33LACNICValid

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.