Network · data from 2026-11-12
AS395257 SINGULARIS-001 - Singularis IT, LLC
Registry name: SINGULARIS-001 - Singularis IT, LLC, US · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS395257, 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.
| 8.39.160.0/24 | No ROA | Other IRR onlyALTDB | 664 99% |
| 199.247.50.0/24 | No ROA | RIR databaseARIN | 671 100% |
| 2604:e6c0::/32 | No ROA | RIR databaseARIN | 635 100% |
AS-SET
AS395257 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 5 are in fix.csv.
- ROA: none3
- Route object: RIR1
- Route object: not announced1
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 8.39.160.0/24 | No ROA covers it. Add a ROA for AS395257, maxLength 24. |
| Route object: RIR | 8.39.160.0/24 | Route object only in ALTDB. Add it in the RIR database for the space. |
| ROA: none | 199.247.50.0/24 | No ROA covers it. Add a ROA for AS395257, maxLength 24. |
| ROA: none | 2604:e6c0::/32 | No ROA covers it. Add a ROA for AS395257, maxLength 32. |
Route objects not announced
Route objects with origin AS395257 whose prefix no peer sees AS395257 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 2001:470:60d::/48 | ARIN | 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.