Network · data from 2026-11-12
AS39826 terc Terc Trade Company d.o.o.
Registry name: terc Terc Trade Company d.o.o., BA · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS39826, 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.155.24.0/22 | No ROA | RIR databaseRIPE | 673 100% |
| 95.133.232.0/22 | No ROA | RIR databaseRIPE | 672 100% |
| 185.84.145.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 94.250.32.0/23 | Valid | RIR databaseRIPE | 671 100% |
| 94.250.33.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 109.175.236.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 109.175.237.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 109.175.238.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 109.175.239.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 185.84.144.0/22 | Valid | RIR databaseRIPE | 671 100% |
| 185.84.144.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 185.84.146.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 185.84.147.0/24 | Valid | RIR databaseRIPE | 671 100% |
AS-SET
AS39826 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 17 are in fix.csv.
- ROA: none2
- Route object: not announced15
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 213.155.24.0/22 | No ROA covers it. Add a ROA for AS39826, maxLength 22. |
| ROA: none | 95.133.232.0/22 | No ROA covers it. Add a ROA for AS39826, maxLength 22. |
Route objects not announced
Route objects with origin AS39826 whose prefix no peer sees AS39826 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 81.93.87.0/24 | RIPE | Invalid: origin |
| 94.250.32.0/24 | RIPE | Invalid: maxLength |
| 95.133.232.0/24 | RIPE | No ROA |
| 95.133.233.0/24 | RIPE | No ROA |
| 95.133.234.0/24 | RIPE | No ROA |
| 95.133.235.0/24 | RIPE | No ROA |
| 109.175.236.0/22 | RIPE | No ROA |
| 109.175.236.0/23 | RIPE | No ROA |
| 109.175.238.0/23 | RIPE | No ROA |
| 185.84.144.0/23 | RIPE | Invalid: maxLength |
| 185.84.146.0/23 | RIPE | Invalid: maxLength |
| 213.155.24.0/24 | RIPE | No ROA |
| 213.155.25.0/24 | RIPE | No ROA |
| 213.155.26.0/24 | RIPE | No ROA |
| 213.155.27.0/24 | 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.