Network · data from 2026-11-12
AS35678 Typoconsult IST ApS
Registry name: Typoconsult IST ApS, DK · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS35678, 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.
| 2a02:188:5108::/48 | Invalid: origin | None | 2 0%low visibility |
| 192.162.4.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 194.117.232.0/23 | No ROA | RIR databaseRIPE | 673 100% |
AS-SET
AS35678 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: origin1
- ROA: none2
- Route object: none1
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: origin | 2a02:188:5108::/48 | ROAs covering it name AS31027, not AS35678. If AS35678 should announce it, add a ROA for AS35678. |
| Route object: none | 2a02:188:5108::/48 | No route object for it. Add a route object with origin AS35678 in the RIR database for the space. |
| ROA: none | 192.162.4.0/24 | No ROA covers it. Add a ROA for AS35678, maxLength 24. |
| ROA: none | 194.117.232.0/23 | No ROA covers it. Add a ROA for AS35678, maxLength 23. |
Route objects not announced
Every route object with origin AS35678 is announced.
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.