Network · data from 2026-11-12
AS43586 INTERLINK UAB Porenta
Registry name: INTERLINK UAB Porenta, LT · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS43586, 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.
| 2a00:1908:c000::/35 | Valid | Other origin only | 635 100% |
| 78.24.76.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 2a00:1908:c000::/36 | Valid | RIR databaseRIPE | 635 100% |
| 2a00:1908:d000::/36 | Valid | RIR databaseRIPE | 635 100% |
AS-SET
AS43586 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.
- Route object: none1
- Route object: not announced4
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 2a00:1908:c000::/35 | Route objects for it name AS3266. Add a route object with origin AS43586 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS43586 whose prefix no peer sees AS43586 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 2a00:1909:1000::/36 | RIPE | Invalid: origin |
| 2a00:1909:2000::/36 | RIPE | Invalid: origin |
| 2a00:1909:3000::/36 | RIPE | Invalid: origin |
| 2a00:190a::/32 | RIPE | Invalid: origin |
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.