Network · data from 2026-11-12
AS61859 Luup Telecomunicações
Registry name: AS61859 - Luup Telecomunicacoes LTDA - ME, BR · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS61859, 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.
| 2804:1a70:8000::/33 | No ROA | Nonecovered by 2804:1a70::/32 | 106 17% |
| 201.149.116.0/22 | No ROA | Other IRR onlyRADB, TC | 672 100% |
| 201.149.116.0/23 | No ROA | Other IRR onlyRADB | 672 100% |
| 201.149.116.0/24 | No ROA | Other IRR onlyRADB | 672 100% |
| 201.149.117.0/24 | No ROA | Other IRR onlyRADB | 672 100% |
| 201.149.118.0/23 | No ROA | Other IRR onlyRADB | 672 100% |
| 201.149.119.0/24 | No ROA | Other IRR onlyRADB | 672 100% |
| 201.149.118.0/24 | No ROA | Other IRR onlyRADB | 671 100% |
| 2804:1a70::/32 | No ROA | Other IRR onlyRADB, TC | 634 100% |
| 2804:1a70::/33 | No ROA | Other IRR onlyRADB | 106 17% |
AS-SET
AS61859's PeeringDB record names no 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 24 are in fix.csv.
- ROA: none10
- Route object: none1
- Route object: RIR9
- Route object: not announced4
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 2804:1a70:8000::/33 | No ROA covers it. Add a ROA for AS61859, maxLength 33. |
| Route object: none | 2804:1a70:8000::/33 | No route object for it. A route object for 2804:1a70::/32 with origin AS61859 covers it (filters allowing more-specifics accept it). Add a route object with origin AS61859 in the RIR database for the space. |
| ROA: none | 201.149.116.0/22 | No ROA covers it. Add a ROA for AS61859, maxLength 22. |
| Route object: RIR | 201.149.116.0/22 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| ROA: none | 201.149.116.0/23 | No ROA covers it. Add a ROA for AS61859, maxLength 23. |
| Route object: RIR | 201.149.116.0/23 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 201.149.116.0/24 | No ROA covers it. Add a ROA for AS61859, maxLength 24. |
| Route object: RIR | 201.149.116.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 201.149.117.0/24 | No ROA covers it. Add a ROA for AS61859, maxLength 24. |
| Route object: RIR | 201.149.117.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 201.149.118.0/23 | No ROA covers it. Add a ROA for AS61859, maxLength 23. |
| Route object: RIR | 201.149.118.0/23 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 201.149.119.0/24 | No ROA covers it. Add a ROA for AS61859, maxLength 24. |
| Route object: RIR | 201.149.119.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 201.149.118.0/24 | No ROA covers it. Add a ROA for AS61859, maxLength 24. |
| Route object: RIR | 201.149.118.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 2804:1a70::/32 | No ROA covers it. Add a ROA for AS61859, maxLength 32. |
| Route object: RIR | 2804:1a70::/32 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| ROA: none | 2804:1a70::/33 | No ROA covers it. Add a ROA for AS61859, maxLength 33. |
| Route object: RIR | 2804:1a70::/33 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS61859 whose prefix no peer sees AS61859 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 2804:1a70::/34 | RADB | No ROA |
| 2804:1a70:4000::/34 | RADB | No ROA |
| 2804:1a70:8000::/34 | RADB | No ROA |
| 2804:1a70:c000::/34 | 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.