Network · data from 2026-11-12
AS61925 AS61925 - MEGABYTE PROVEDOR DE INTERNET LTDA
Registry name: AS61925 - MEGABYTE PROVEDOR DE INTERNET LTDA, BR · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS61925, 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.
| 190.107.196.0/24 | No ROA | Nonecovered by 190.107.196.0/22 | 666 99% |
| 190.107.197.0/24 | No ROA | Nonecovered by 190.107.196.0/22 | 666 99% |
| 190.107.198.0/24 | No ROA | Nonecovered by 190.107.196.0/22 | 666 99% |
| 190.107.199.0/24 | No ROA | Nonecovered by 190.107.196.0/22 | 664 99% |
| 190.107.192.0/24 | No ROA | Nonecovered by 190.107.192.0/22 | 661 98% |
| 190.107.193.0/24 | No ROA | Other IRR onlyRADB | 669 99% |
| 190.107.196.0/22 | No ROA | Other IRR onlyRADB | 666 99% |
| 2804:1838::/36 | No ROA | Other IRR onlyRADB | 633 100% |
| 2804:1838:8000::/36 | No ROA | Other IRR onlyRADB | 633 100% |
| 2804:1838:e000::/36 | No ROA | Other IRR onlyRADB | 632 99% |
AS-SET
AS61925 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 27 are in fix.csv.
- ROA: none10
- Route object: none5
- Route object: RIR5
- Route object: not announced7
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 190.107.196.0/24 | No ROA covers it. Add a ROA for AS61925, maxLength 24. |
| Route object: none | 190.107.196.0/24 | No route object for it. A route object for 190.107.196.0/22 with origin AS61925 covers it (filters allowing more-specifics accept it). Add a route object with origin AS61925 in the RIR database for the space. |
| ROA: none | 190.107.197.0/24 | No ROA covers it. Add a ROA for AS61925, maxLength 24. |
| Route object: none | 190.107.197.0/24 | No route object for it. A route object for 190.107.196.0/22 with origin AS61925 covers it (filters allowing more-specifics accept it). Add a route object with origin AS61925 in the RIR database for the space. |
| ROA: none | 190.107.198.0/24 | No ROA covers it. Add a ROA for AS61925, maxLength 24. |
| Route object: none | 190.107.198.0/24 | No route object for it. A route object for 190.107.196.0/22 with origin AS61925 covers it (filters allowing more-specifics accept it). Add a route object with origin AS61925 in the RIR database for the space. |
| ROA: none | 190.107.199.0/24 | No ROA covers it. Add a ROA for AS61925, maxLength 24. |
| Route object: none | 190.107.199.0/24 | No route object for it. A route object for 190.107.196.0/22 with origin AS61925 covers it (filters allowing more-specifics accept it). Add a route object with origin AS61925 in the RIR database for the space. |
| ROA: none | 190.107.192.0/24 | No ROA covers it. Add a ROA for AS61925, maxLength 24. |
| Route object: none | 190.107.192.0/24 | No route object for it. A route object for 190.107.192.0/22 with origin AS61925 covers it (filters allowing more-specifics accept it). Add a route object with origin AS61925 in the RIR database for the space. |
| ROA: none | 190.107.193.0/24 | No ROA covers it. Add a ROA for AS61925, maxLength 24. |
| Route object: RIR | 190.107.193.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 190.107.196.0/22 | No ROA covers it. Add a ROA for AS61925, maxLength 22. |
| Route object: RIR | 190.107.196.0/22 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 2804:1838::/36 | No ROA covers it. Add a ROA for AS61925, maxLength 36. |
| Route object: RIR | 2804:1838::/36 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 2804:1838:8000::/36 | No ROA covers it. Add a ROA for AS61925, maxLength 36. |
| Route object: RIR | 2804:1838:8000::/36 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 2804:1838:e000::/36 | No ROA covers it. Add a ROA for AS61925, maxLength 36. |
| Route object: RIR | 2804:1838:e000::/36 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS61925 whose prefix no peer sees AS61925 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 190.107.192.0/20 | RADB | No ROA |
| 190.107.192.0/22 | RADB | No ROA |
| 190.107.194.0/23 | RADB | No ROA |
| 190.107.200.0/21 | RADB | No ROA |
| 190.107.200.0/22 | RADB | No ROA |
| 190.107.204.0/22 | RADB | No ROA |
| 2804:1838::/32 | 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.