bgpreport

Network · data from 2026-11-12

AS13079 ZONDH Zond Holding JSC

Registry name: ZONDH Zond Holding JSC, RU · not in PeeringDB

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

Announced routes

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

213.168.128.0/19 Valid RIR databaseRIPE 673 100% 67
213.168.156.0/24 Valid RIR databaseRIPE 671 100% 66

AS-SET

AS13079 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 61 are in fix.csv.

  • Route object: not announced61

Route objects not announced

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

213.168.128.0/20RIPEValid
213.168.128.0/21RIPEValid
213.168.128.0/22RIPEValid
213.168.128.0/23RIPEValid
213.168.128.0/24RIPEValid
213.168.129.0/24RIPEValid
213.168.130.0/23RIPEValid
213.168.130.0/24RIPEValid
213.168.131.0/24RIPEValid
213.168.132.0/22RIPEValid
213.168.132.0/23RIPEValid
213.168.132.0/24RIPEValid
213.168.133.0/24RIPEValid
213.168.134.0/23RIPEValid
213.168.134.0/24RIPEValid
213.168.135.0/24RIPEValid
213.168.136.0/21RIPEValid
213.168.136.0/22RIPEValid
213.168.136.0/23RIPEValid
213.168.136.0/24RIPEValid
213.168.137.0/24RIPEValid
213.168.138.0/23RIPEValid
213.168.138.0/24RIPEValid
213.168.139.0/24RIPEValid
213.168.140.0/22RIPEValid
213.168.140.0/23RIPEValid
213.168.140.0/24RIPEValid
213.168.141.0/24RIPEValid
213.168.142.0/23RIPEValid
213.168.142.0/24RIPEValid
213.168.143.0/24RIPEValid
213.168.144.0/20RIPEValid
213.168.144.0/21RIPEValid
213.168.144.0/22RIPEValid
213.168.144.0/23RIPEValid
213.168.144.0/24RIPEValid
213.168.145.0/24RIPEValid
213.168.146.0/23RIPEValid
213.168.146.0/24RIPEValid
213.168.147.0/24RIPEValid
213.168.148.0/22RIPEValid
213.168.148.0/23RIPEValid
213.168.148.0/24RIPEValid
213.168.149.0/24RIPEValid
213.168.150.0/23RIPEValid
213.168.150.0/24RIPEValid
213.168.151.0/24RIPEValid
213.168.152.0/21RIPEValid
213.168.152.0/22RIPEValid
213.168.152.0/23RIPEValid
213.168.152.0/24RIPEValid
213.168.153.0/24RIPEValid
213.168.154.0/23RIPEValid
213.168.154.0/24RIPEValid
213.168.155.0/24RIPEValid
213.168.156.0/22RIPEValid
213.168.156.0/23RIPEValid
213.168.157.0/24RIPEValid
213.168.158.0/23RIPEValid
213.168.158.0/24RIPEValid
213.168.159.0/24RIPEValid

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.