Network · data from 2026-11-12
AS207291 SENDER-AS UAB Sender.lt
Registry name: SENDER-AS UAB Sender.lt, LT · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS207291, 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.
| 141.136.38.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 2.57.236.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 141.136.40.0/24 | Valid | RIR databaseRIPE | 673 100% |
AS-SET
AS207291 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: none1
- Route object: not announced4
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 141.136.38.0/24 | No ROA covers it. Add a ROA for AS207291, maxLength 24. |
Route objects not announced
Route objects with origin AS207291 whose prefix no peer sees AS207291 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 195.191.140.0/24 | RIPE | Valid |
| 195.191.141.0/24 | RIPE | No ROA |
| 195.191.176.0/24 | RIPE | Valid |
| 195.191.177.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.