Network · data from 2026-11-12
AS44712 eHAMnet
Registry name: eHAMnet-AS eHAMnet, s.r.o., CZ · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS44712, 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.
| 151.249.110.0/23 | Valid | Nonecovered by 151.249.108.0/22 | 673 100% |
| 151.249.104.0/21 | Valid | RIR databaseRIPE | 673 100% |
| 2a01:a8c0::/29 | Valid | RIR databaseRIPE | 634 100% |
AS-SET
PeeringDB's irr_as_set for AS44712: RIPE::AS44712. Expanded from the day's IRR dumps the way bgpq4 does against whois.radb.net: a name with a database is read from that database only, one without from the first database in RADB's order. "Not covered" = this network's own routes that a filter built from the set would leave out (AS44712 isn't in the set, or no route object for AS44712 covers the route; more-specifics of a route object are accepted down to /24 and /48, as with bgpq4 -A -R 24 / -R 48). Customers' routes aren't counted: the collectors show each route's origin, not which network it came through.
| Name | Database | ASNs | Sets | AS44712 in it | Not covered | |
|---|---|---|---|---|---|---|
| RIPE::AS44712 | A single AS number, not a set: AS44712 (this network), 5 route objects. | |||||
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: none1
- Route object: not announced3
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 151.249.110.0/23 | No route object for it. A route object for 151.249.108.0/22 with origin AS44712 covers it (filters allowing more-specifics accept it). Add a route object with origin AS44712 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS44712 whose prefix no peer sees AS44712 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 151.249.104.0/23 | RIPE | Valid |
| 151.249.107.0/24 | RIPE | Valid |
| 151.249.108.0/22 | RIPE | Valid |
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.