Network · data from 2026-11-12
AS209836 NHCO Toesegaran Shabakeh Arseh Novin Ltd
Registry name: NHCO Toesegaran Shabakeh Arseh Novin Ltd, IR · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS209836, 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.
| 212.80.11.0/24 | Invalid: origin | Other origin only | 3 0%low visibility |
| 193.105.6.0/24 | No ROA | RIR databaseRIPE | 672 100% |
| 194.225.146.0/24 | Valid | Other origin onlycovered by 194.225.146.0/23 | 672 100% |
| 194.225.147.0/24 | Valid | Other origin onlycovered by 194.225.146.0/23 | 672 100% |
| 185.126.201.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 185.126.200.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 194.225.145.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 194.225.158.0/23 | Valid | RIR databaseRIPE | 672 100% |
| 213.232.124.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 213.232.125.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 213.232.126.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 213.232.127.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 5.160.46.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 77.104.94.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 194.225.157.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 77.237.73.0/24 | Valid | RIR databaseRIPE | 669 99% |
| 87.107.39.0/24 | Valid | RIR databaseRIPE | 669 99% |
| 185.209.42.0/24 | Valid | RIR databaseRIPE | 669 99% |
| 185.228.59.0/24 | Valid | RIR databaseRIPE | 669 99% |
| 185.235.198.0/24 | Valid | RIR databaseRIPE | 669 99% |
| 77.74.202.0/24 | Valid | RIR databaseRIPE | 668 99% |
| 2a0a:2fc0::/30 | Valid | RIR databaseRIPE | 2 0%low visibility |
| 194.225.146.0/23 | Valid | RIR databaseRIPE | 1 0%low visibility |
AS-SET
AS209836 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 7 are in fix.csv.
- ROA: origin1
- ROA: none1
- Route object: none3
- Route object: not announced2
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: origin | 212.80.11.0/24 | ROAs covering it name AS34837, AS44889, not AS209836. If AS209836 should announce it, add a ROA for AS209836. |
| Route object: none | 212.80.11.0/24 | Route objects for it name AS44889. Add a route object with origin AS209836 in the RIR database for the space. |
| ROA: none | 193.105.6.0/24 | No ROA covers it. Add a ROA for AS209836, maxLength 24. |
| Route object: none | 194.225.146.0/24 | Route objects for it name AS6736. A route object for 194.225.146.0/23 with origin AS209836 covers it (filters allowing more-specifics accept it). Add a route object with origin AS209836 in the RIR database for the space. |
| Route object: none | 194.225.147.0/24 | Route objects for it name AS6736. A route object for 194.225.146.0/23 with origin AS209836 covers it (filters allowing more-specifics accept it). Add a route object with origin AS209836 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS209836 whose prefix no peer sees AS209836 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 2a13:6b00::/32 | RIPE | Valid |
| 2a13:6b01::/32 | RIPE | No ROA |
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.