Network · data from 2026-11-12
AS61625 Grupo We Dev LTDA
Registry name: AS61625 - Grupo We Dev LTDA, BR · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS61625, 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.
| 64.204.232.0/21 | No ROA | None | 2 0%low visibility |
| 2804:9524:4080::/42 | Valid | Nonecovered by 2804:9524::/32 | 629 99% |
| 2804:9524:4240::/42 | Valid | Nonecovered by 2804:9524::/32 | 606 95% |
| 2804:9524:4280::/42 | Valid | Nonecovered by 2804:9524::/32 | 606 95% |
| 2804:9524:4040::/42 | Valid | Nonecovered by 2804:9524::/32 | 603 95% |
| 2804:9524:4300::/42 | Valid | Nonecovered by 2804:9524::/32 | 603 95% |
| 2804:9524:4100::/42 | Valid | Other IRR onlyALTDB, RADB | 611 96% |
| 2804:9524::/32 | Valid | Other IRR onlyRADB, TC | 609 96% |
| 2804:9524:4000::/42 | Valid | Other IRR onlyALTDB, RADB | 605 95% |
| 2804:9524:4140::/42 | Valid | Other IRR onlyRADB | 605 95% |
| 2804:9524:4180::/42 | Valid | Other IRR onlyRADB | 602 95% |
| 206.62.68.0/24 | Valid | RIR databaseARIN | 671 100% |
| 38.93.53.0/24 | Valid | RIR databaseARIN | 668 99% |
| 206.62.68.0/22 | Valid | RIR databaseARIN | 668 99% |
| 209.61.63.0/24 | Valid | RIR databaseALTDB, ARIN, RADB | 668 99% |
| 206.62.71.0/24 | Valid | RIR databaseARIN, RADB | 667 99% |
| 38.93.50.0/24 | Valid | RIR databaseARIN | 666 99% |
| 38.93.52.0/24 | Valid | RIR databaseARIN | 666 99% |
| 38.93.54.0/24 | Valid | RIR databaseARIN | 666 99% |
| 209.61.61.0/24 | Valid | RIR databaseALTDB, ARIN | 666 99% |
| 38.93.51.0/24 | Valid | RIR databaseARIN | 665 99% |
| 38.93.55.0/24 | Valid | RIR databaseARIN | 665 99% |
| 209.61.60.0/24 | Valid | RIR databaseARIN | 662 98% |
| 209.61.62.0/24 | Valid | RIR databaseALTDB, ARIN | 662 98% |
| 38.93.48.0/24 | Valid | RIR databaseARIN, RADB | 661 98% |
| 38.93.49.0/24 | Valid | RIR databaseARIN, RADB | 661 98% |
| 206.62.69.0/24 | Valid | RIR databaseARIN, RADB | 661 98% |
AS-SET
PeeringDB's irr_as_set for AS61625: AS61625:AS-ALL. Expanded from the day's IRR dumps the way bgpq4 does against whois.radb.net: a name with a database is read from that database only, one without from the first database in RADB's order. "Not covered" = this network's own routes that a filter built from the set would leave out (AS61625 isn't in the set, or no route object for AS61625 covers the route; more-specifics of a route object are accepted down to /24 and /48, as with bgpq4 -A -R 24 / -R 48). Customers' routes aren't counted: the collectors show each route's origin, not which network it came through.
| Name | Database | ASNs | Sets | AS61625 in it | Not covered |
|---|---|---|---|---|---|
| AS61625:AS-ALL | TClists itself further down1 member set in no database: AS-264354 | 76 | 16 | Yes | 1 |
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: none1
- Route object: none6
- Route object: RIR5
- AS-SET: missing member1
- Route object: not announced14
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 64.204.232.0/21 | No ROA covers it. Add a ROA for AS61625, maxLength 21. |
| Route object: none | 64.204.232.0/21 | No route object for it. Add a route object with origin AS61625 in the RIR database for the space. |
| Route object: none | 2804:9524:4080::/42 | No route object for it. A route object for 2804:9524::/32 with origin AS61625 covers it (filters allowing more-specifics accept it). Add a route object with origin AS61625 in the RIR database for the space. |
| Route object: none | 2804:9524:4240::/42 | No route object for it. A route object for 2804:9524::/32 with origin AS61625 covers it (filters allowing more-specifics accept it). Add a route object with origin AS61625 in the RIR database for the space. |
| Route object: none | 2804:9524:4280::/42 | No route object for it. A route object for 2804:9524::/32 with origin AS61625 covers it (filters allowing more-specifics accept it). Add a route object with origin AS61625 in the RIR database for the space. |
| Route object: none | 2804:9524:4040::/42 | No route object for it. A route object for 2804:9524::/32 with origin AS61625 covers it (filters allowing more-specifics accept it). Add a route object with origin AS61625 in the RIR database for the space. |
| Route object: none | 2804:9524:4300::/42 | No route object for it. A route object for 2804:9524::/32 with origin AS61625 covers it (filters allowing more-specifics accept it). Add a route object with origin AS61625 in the RIR database for the space. |
| Route object: RIR | 2804:9524:4100::/42 | Route object only in ALTDB, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 2804:9524::/32 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 2804:9524:4000::/42 | Route object only in ALTDB, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 2804:9524:4140::/42 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 2804:9524:4180::/42 | Route object only in RADB. Add it in the RIR database for the space. |
| AS-SET: missing member | AS61625:AS-ALL | AS61625:AS-ALL (TC) lists AS-264354; no IRR database read has it. |
Route objects not announced
Route objects with origin AS61625 whose prefix no peer sees AS61625 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 38.93.48.0/21 | ARIN | Valid |
| 38.93.48.0/22 | ARIN | Valid |
| 38.93.48.0/23 | ARIN | Valid |
| 38.93.50.0/23 | ARIN | Valid |
| 38.93.52.0/22 | ARIN | Valid |
| 38.93.52.0/23 | ARIN | Valid |
| 38.93.54.0/23 | ARIN | Valid |
| 206.62.68.0/23 | ARIN | Valid |
| 206.62.70.0/23 | ARIN | Valid |
| 206.62.70.0/24 | ARIN | Valid |
| 209.61.60.0/22 | ARIN, RADB | Valid |
| 209.61.60.0/23 | ALTDB, ARIN | Valid |
| 209.61.62.0/23 | ALTDB, ARIN | Valid |
| 2804:9524:41c0::/42 | RADB | 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.