Network · data from 2026-11-12
AS271641 AS271641 - ANDERSON L. DA SILVA MULTIMIDIA - @NET
Registry name: AS271641 - ANDERSON L. DA SILVA MULTIMIDIA - @NET, BR · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS271641, 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.
| 200.194.188.0/23 | Valid | Nonecovered by 200.194.188.0/22 | 670 100% |
| 200.194.190.0/24 | Valid | Nonecovered by 200.194.188.0/22 | 670 100% |
| 2804:7eb0::/33 | Valid | Nonecovered by 2804:7eb0::/32 | 632 99% |
| 2804:7eb0::/34 | Valid | Nonecovered by 2804:7eb0::/32 | 631 99% |
| 2804:7eb0:4000::/34 | Valid | Nonecovered by 2804:7eb0::/32 | 631 99% |
| 2804:7eb0:8000::/34 | Valid | Nonecovered by 2804:7eb0::/32 | 631 99% |
| 200.194.188.0/24 | Valid | Nonecovered by 200.194.188.0/22 | 201 30% |
| 200.194.189.0/24 | Valid | Nonecovered by 200.194.188.0/22 | 199 30% |
| 2804:7eb0:c000::/34 | Valid | Other IRR onlyRADB | 635 100% |
AS-SET
AS271641 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 12 are in fix.csv.
- Route object: none8
- Route object: RIR1
- Route object: not announced3
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 200.194.188.0/23 | No route object for it. A route object for 200.194.188.0/22 with origin AS271641 covers it (filters allowing more-specifics accept it). Add a route object with origin AS271641 in the RIR database for the space. |
| Route object: none | 200.194.190.0/24 | No route object for it. A route object for 200.194.188.0/22 with origin AS271641 covers it (filters allowing more-specifics accept it). Add a route object with origin AS271641 in the RIR database for the space. |
| Route object: none | 2804:7eb0::/33 | No route object for it. A route object for 2804:7eb0::/32 with origin AS271641 covers it (filters allowing more-specifics accept it). Add a route object with origin AS271641 in the RIR database for the space. |
| Route object: none | 2804:7eb0::/34 | No route object for it. A route object for 2804:7eb0::/32 with origin AS271641 covers it (filters allowing more-specifics accept it). Add a route object with origin AS271641 in the RIR database for the space. |
| Route object: none | 2804:7eb0:4000::/34 | No route object for it. A route object for 2804:7eb0::/32 with origin AS271641 covers it (filters allowing more-specifics accept it). Add a route object with origin AS271641 in the RIR database for the space. |
| Route object: none | 2804:7eb0:8000::/34 | No route object for it. A route object for 2804:7eb0::/32 with origin AS271641 covers it (filters allowing more-specifics accept it). Add a route object with origin AS271641 in the RIR database for the space. |
| Route object: none | 200.194.188.0/24 | No route object for it. A route object for 200.194.188.0/22 with origin AS271641 covers it (filters allowing more-specifics accept it). Add a route object with origin AS271641 in the RIR database for the space. |
| Route object: none | 200.194.189.0/24 | No route object for it. A route object for 200.194.188.0/22 with origin AS271641 covers it (filters allowing more-specifics accept it). Add a route object with origin AS271641 in the RIR database for the space. |
| Route object: RIR | 2804:7eb0:c000::/34 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS271641 whose prefix no peer sees AS271641 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 200.194.188.0/22 | RADB, TC | Valid |
| 200.194.191.0/24 | RADB | Valid |
| 2804:7eb0::/32 | RADB, TC | Valid |
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.