Network · data from 2026-11-12
AS14786 ALLURETELECOM - Allure Telecom Inc
Registry name: ALLURETELECOM - Allure Telecom Inc, US · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS14786, 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.
| 38.83.94.0/24 | No ROA | Other IRR onlyRADB | 669 99% |
| 38.100.200.0/24 | Valid | RIR databaseARIN | 672 100% |
AS-SET
AS14786 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 4 are in fix.csv.
- ROA: none1
- Route object: RIR1
- Route object: not announced2
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 38.83.94.0/24 | No ROA covers it. Add a ROA for AS14786, maxLength 24. |
| Route object: RIR | 38.83.94.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS14786 whose prefix no peer sees AS14786 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 192.234.219.0/24 | RADB | No ROA |
| 208.62.94.0/24 | RADB | 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.