Network · data from 2026-11-12
AS218701 HATAM-AS HATAM AM SHOP LLC
Registry name: HATAM-AS HATAM AM SHOP LLC, US · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS218701, 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.
| 82.38.46.0/24 | Valid | Nonecovered by 82.38.46.0/23 | 535 79% |
| 82.38.47.0/24 | Valid | Nonecovered by 82.38.46.0/23 | 535 79% |
| 82.38.80.0/24 | Valid | Nonecovered by 82.38.80.0/23 | 535 79% |
| 82.38.81.0/24 | Valid | Nonecovered by 82.38.80.0/23 | 535 79% |
| 194.77.76.0/24 | Valid | Nonecovered by 194.77.76.0/23 | 166 25% |
| 194.77.77.0/24 | Valid | Nonecovered by 194.77.76.0/23 | 166 25% |
| 194.77.76.0/23 | Valid | Other IRR onlyRADB | 165 25% |
| 82.38.46.0/23 | Valid | RIR databaseRADB, RIPE | 653 97% |
| 82.38.80.0/23 | Valid | RIR databaseRADB, RIPE | 653 97% |
| 143.20.70.0/23 | Valid | RIR databaseRADB, RIPE | 653 97% |
AS-SET
AS218701 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.
- Route object: none6
- Route object: RIR1
- Route object: not announced5
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 82.38.46.0/24 | No route object for it. A route object for 82.38.46.0/23 with origin AS218701 covers it (filters allowing more-specifics accept it). Add a route object with origin AS218701 in the RIR database for the space. |
| Route object: none | 82.38.47.0/24 | No route object for it. A route object for 82.38.46.0/23 with origin AS218701 covers it (filters allowing more-specifics accept it). Add a route object with origin AS218701 in the RIR database for the space. |
| Route object: none | 82.38.80.0/24 | No route object for it. A route object for 82.38.80.0/23 with origin AS218701 covers it (filters allowing more-specifics accept it). Add a route object with origin AS218701 in the RIR database for the space. |
| Route object: none | 82.38.81.0/24 | No route object for it. A route object for 82.38.80.0/23 with origin AS218701 covers it (filters allowing more-specifics accept it). Add a route object with origin AS218701 in the RIR database for the space. |
| Route object: none | 194.77.76.0/24 | No route object for it. A route object for 194.77.76.0/23 with origin AS218701 covers it (filters allowing more-specifics accept it). Add a route object with origin AS218701 in the RIR database for the space. |
| Route object: none | 194.77.77.0/24 | No route object for it. A route object for 194.77.76.0/23 with origin AS218701 covers it (filters allowing more-specifics accept it). Add a route object with origin AS218701 in the RIR database for the space. |
| Route object: RIR | 194.77.76.0/23 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS218701 whose prefix no peer sees AS218701 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 82.38.7.0/24 | RADB, RIPE | Valid |
| 82.38.42.0/23 | RADB, RIPE | Valid |
| 178.83.82.0/23 | RADB, RIPE | Valid |
| 222.167.198.0/24 | RADB, RIPE | Valid |
| 2a0a:d687:ff06::/48 | 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.