Network · data from 2026-11-12
AS42964 SIGMANET-HU-AS SigmaNet Szolgaltato es Kereskedelm Ltd
Registry name: SIGMANET-HU-AS SigmaNet Szolgaltato es Kereskedelm Ltd, HU · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS42964, 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.
| 2a02:730:1::/48 | Valid | None | 636 100% |
| 79.172.206.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 79.172.215.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 79.172.217.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 79.172.237.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 87.229.98.0/23 | Valid | RIR databaseRIPE | 673 100% |
| 87.229.102.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 178.238.223.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 213.181.222.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 217.144.61.0/24 | Valid | RIR databaseRIPE | 673 100% |
AS-SET
AS42964 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 1 are in fix.csv.
- Route object: none1
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 2a02:730:1::/48 | No route object for it. Add a route object with origin AS42964 in the RIR database for the space. |
Route objects not announced
Every route object with origin AS42964 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.