Network · data from 2026-11-12
AS262503 WIKI TELECOMUNICAÇÕES
Registry name: AS262503 - WIKI TELECOMUNICACOES EIRELI, BR · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS262503, 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.
| 38.236.74.0/24 | Valid | Nonecovered by 38.236.72.0/21 | 671 100% |
| 2804:2be0:1200::/40 | Valid | Nonecovered by 2804:2be0::/32 | 636 100% |
| 2804:2be0:3400::/40 | Valid | Nonecovered by 2804:2be0::/32 | 636 100% |
| 2804:2be0:7200::/40 | Valid | Nonecovered by 2804:2be0::/32 | 636 100% |
| 2804:2be0:7300::/40 | Valid | Nonecovered by 2804:2be0::/32 | 636 100% |
| 2804:2be0:8000::/40 | Valid | Nonecovered by 2804:2be0::/32 | 635 100% |
| 2804:2be0:9000::/40 | Valid | Nonecovered by 2804:2be0::/32 | 635 100% |
| 2804:2be0:9200::/40 | Valid | Nonecovered by 2804:2be0::/32 | 635 100% |
| 2804:2be0:9800::/40 | Valid | Nonecovered by 2804:2be0::/32 | 335 53% |
| 38.236.73.0/24 | Valid | Nonecovered by 38.236.72.0/21 | 2 0%low visibility |
| 45.181.228.0/24 | Valid | Other IRR onlyRADB | 672 100% |
| 45.181.229.0/24 | Valid | Other IRR onlyRADB | 672 100% |
| 45.181.231.0/24 | Valid | Other IRR onlyRADB | 672 100% |
| 167.249.168.0/24 | Valid | Other IRR onlyRADB | 672 100% |
| 167.249.169.0/24 | Valid | Other IRR onlyRADB | 672 100% |
| 167.249.170.0/24 | Valid | Other IRR onlyRADB | 672 100% |
| 167.249.171.0/24 | Valid | Other IRR onlyRADB | 672 100% |
| 177.66.192.0/24 | Valid | Other IRR onlyRADB | 672 100% |
| 177.66.193.0/24 | Valid | Other IRR onlyRADB | 672 100% |
| 177.66.194.0/24 | Valid | Other IRR onlyRADB | 672 100% |
| 177.66.195.0/24 | Valid | Other IRR onlyRADB | 672 100% |
| 177.91.52.0/24 | Valid | Other IRR onlyRADB | 672 100% |
| 177.91.53.0/24 | Valid | Other IRR onlyRADB | 672 100% |
| 177.91.54.0/24 | Valid | Other IRR onlyRADB | 672 100% |
| 177.91.55.0/24 | Valid | Other IRR onlyRADB | 672 100% |
| 205.164.232.0/24 | Valid | Other IRR onlyRADB | 672 100% |
| 205.164.233.0/24 | Valid | Other IRR onlyRADB | 672 100% |
| 205.164.234.0/24 | Valid | Other IRR onlyRADB | 672 100% |
| 205.164.235.0/24 | Valid | Other IRR onlyRADB | 672 100% |
| 205.164.236.0/24 | Valid | Other IRR onlyRADB | 672 100% |
| 205.164.237.0/24 | Valid | Other IRR onlyRADB | 672 100% |
| 205.164.238.0/24 | Valid | Other IRR onlyRADB | 672 100% |
| 205.164.239.0/24 | Valid | Other IRR onlyRADB | 672 100% |
| 38.236.72.0/24 | Valid | Other IRR onlyRADB | 671 100% |
| 45.181.230.0/24 | Valid | Other IRR onlyRADB | 670 100% |
| 2804:2be0::/32 | Valid | Other IRR onlyRADB, TC | 636 100% |
| 2804:2be0:7100::/40 | Valid | Other IRR onlyRADB | 636 100% |
AS-SET
PeeringDB's irr_as_set for AS262503: AS-WIKI-TELECOM. 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 (AS262503 isn't in the set, or no route object for AS262503 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 | AS262503 in it | Not covered |
|---|---|---|---|---|---|
| AS-WIKI-TELECOM | RADB2 member sets in no database: AS269090:AS-CUSTOMERS, AS272772:AS-CUSTOMERS | 69 | 28 | Yes | 0 |
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 45 are in fix.csv.
- Route object: none10
- Route object: RIR27
- AS-SET: missing member2
- Route object: not announced6
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 38.236.74.0/24 | No route object for it. A route object for 38.236.72.0/21 with origin AS262503 covers it (filters allowing more-specifics accept it). Add a route object with origin AS262503 in the RIR database for the space. |
| Route object: none | 2804:2be0:1200::/40 | No route object for it. A route object for 2804:2be0::/32 with origin AS262503 covers it (filters allowing more-specifics accept it). Add a route object with origin AS262503 in the RIR database for the space. |
| Route object: none | 2804:2be0:3400::/40 | No route object for it. A route object for 2804:2be0::/32 with origin AS262503 covers it (filters allowing more-specifics accept it). Add a route object with origin AS262503 in the RIR database for the space. |
| Route object: none | 2804:2be0:7200::/40 | No route object for it. A route object for 2804:2be0::/32 with origin AS262503 covers it (filters allowing more-specifics accept it). Add a route object with origin AS262503 in the RIR database for the space. |
| Route object: none | 2804:2be0:7300::/40 | No route object for it. A route object for 2804:2be0::/32 with origin AS262503 covers it (filters allowing more-specifics accept it). Add a route object with origin AS262503 in the RIR database for the space. |
| Route object: none | 2804:2be0:8000::/40 | No route object for it. A route object for 2804:2be0::/32 with origin AS262503 covers it (filters allowing more-specifics accept it). Add a route object with origin AS262503 in the RIR database for the space. |
| Route object: none | 2804:2be0:9000::/40 | No route object for it. A route object for 2804:2be0::/32 with origin AS262503 covers it (filters allowing more-specifics accept it). Add a route object with origin AS262503 in the RIR database for the space. |
| Route object: none | 2804:2be0:9200::/40 | No route object for it. A route object for 2804:2be0::/32 with origin AS262503 covers it (filters allowing more-specifics accept it). Add a route object with origin AS262503 in the RIR database for the space. |
| Route object: none | 2804:2be0:9800::/40 | No route object for it. A route object for 2804:2be0::/32 with origin AS262503 covers it (filters allowing more-specifics accept it). Add a route object with origin AS262503 in the RIR database for the space. |
| Route object: none | 38.236.73.0/24 | No route object for it. A route object for 38.236.72.0/21 with origin AS262503 covers it (filters allowing more-specifics accept it). Add a route object with origin AS262503 in the RIR database for the space. |
| Route object: RIR | 45.181.228.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 45.181.229.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 45.181.231.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 167.249.168.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 167.249.169.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 167.249.170.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 167.249.171.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 177.66.192.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 177.66.193.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 177.66.194.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 177.66.195.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 177.91.52.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 177.91.53.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 177.91.54.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 177.91.55.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 205.164.232.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 205.164.233.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 205.164.234.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 205.164.235.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 205.164.236.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 205.164.237.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 205.164.238.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 205.164.239.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 38.236.72.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 45.181.230.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 2804:2be0::/32 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 2804:2be0:7100::/40 | Route object only in RADB. Add it in the RIR database for the space. |
| AS-SET: missing member | AS-WIKI-TELECOM | AS-WIKI-TELECOM (RADB) lists AS269090:AS-CUSTOMERS; no IRR database read has it. |
| AS-SET: missing member | AS-WIKI-TELECOM | AS-WIKI-TELECOM (RADB) lists AS272772:AS-CUSTOMERS; no IRR database read has it. |
Route objects not announced
Route objects with origin AS262503 whose prefix no peer sees AS262503 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 38.236.72.0/21 | ARIN | Valid |
| 45.181.228.0/22 | RADB | Valid |
| 167.249.168.0/22 | RADB, TC | Valid |
| 177.66.192.0/22 | RADB, TC | Valid |
| 177.91.52.0/22 | RADB | Valid |
| 205.164.232.0/21 | ARIN, 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.