Network · data from 2026-11-12
AS52973 YIP Telecom
Registry name: AS52973 - YIPI Telecom LTDA., BR · PeeringDB
31IPv4 routes
100.0% RPKI valid · 9.7% with a route object
1IPv6 routes
100.0% RPKI valid · 100.0% with a route object
0RPKI invalid
0 origin · 0 maxLength
0No ROA
28 with no route object for this origin
0Low visibility
seen by under 10% of full-table peers
0Route objects not announced
registered with origin AS52973, seen from no peer
Announced routes
Every prefix a peer of the route collectors sees with origin AS52973, 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.
| 186.216.196.0/24 | Valid | Nonecovered by 186.216.192.0/21 | 673 100% |
| 186.216.204.0/24 | Valid | Nonecovered by 186.216.200.0/21 | 667 99% |
| 186.216.192.0/22 | Valid | Nonecovered by 186.216.192.0/21 | 208 31% |
| 186.216.192.0/23 | Valid | Nonecovered by 186.216.192.0/21 | 208 31% |
| 186.216.194.0/23 | Valid | Nonecovered by 186.216.192.0/21 | 208 31% |
| 186.216.196.0/22 | Valid | Nonecovered by 186.216.192.0/21 | 208 31% |
| 186.216.196.0/23 | Valid | Nonecovered by 186.216.192.0/21 | 208 31% |
| 186.216.198.0/23 | Valid | Nonecovered by 186.216.192.0/21 | 208 31% |
| 186.216.200.0/22 | Valid | Nonecovered by 186.216.200.0/21 | 208 31% |
| 186.216.200.0/23 | Valid | Nonecovered by 186.216.200.0/21 | 208 31% |
| 186.216.202.0/23 | Valid | Nonecovered by 186.216.200.0/21 | 208 31% |
| 186.216.204.0/22 | Valid | Nonecovered by 186.216.200.0/21 | 208 31% |
| 186.216.204.0/23 | Valid | Nonecovered by 186.216.200.0/21 | 208 31% |
| 186.216.206.0/23 | Valid | Nonecovered by 186.216.200.0/21 | 208 31% |
| 186.216.192.0/24 | Valid | Nonecovered by 186.216.192.0/21 | 98 15% |
| 186.216.193.0/24 | Valid | Nonecovered by 186.216.192.0/21 | 98 15% |
| 186.216.194.0/24 | Valid | Nonecovered by 186.216.192.0/21 | 98 15% |
| 186.216.195.0/24 | Valid | Nonecovered by 186.216.192.0/21 | 98 15% |
| 186.216.197.0/24 | Valid | Nonecovered by 186.216.192.0/21 | 98 15% |
| 186.216.198.0/24 | Valid | Nonecovered by 186.216.192.0/21 | 98 15% |
| 186.216.199.0/24 | Valid | Nonecovered by 186.216.192.0/21 | 98 15% |
| 186.216.200.0/24 | Valid | Nonecovered by 186.216.200.0/21 | 98 15% |
| 186.216.201.0/24 | Valid | Nonecovered by 186.216.200.0/21 | 98 15% |
| 186.216.202.0/24 | Valid | Nonecovered by 186.216.200.0/21 | 98 15% |
| 186.216.203.0/24 | Valid | Nonecovered by 186.216.200.0/21 | 98 15% |
| 186.216.205.0/24 | Valid | Nonecovered by 186.216.200.0/21 | 98 15% |
| 186.216.206.0/24 | Valid | Nonecovered by 186.216.200.0/21 | 98 15% |
| 186.216.207.0/24 | Valid | Nonecovered by 186.216.200.0/21 | 98 15% |
| 186.216.192.0/20 | Valid | Other IRR onlyALTDB, RADB | 669 99% |
| 186.216.192.0/21 | Valid | Other IRR onlyRADB | 669 99% |
| 186.216.200.0/21 | Valid | Other IRR onlyRADB | 669 99% |
| 2804:3b00::/32 | Valid | Other IRR onlyALTDB, TC | 635 100% |
AS-SET
PeeringDB's irr_as_set for AS52973: AS-52973-GLOBAL. 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 (AS52973 isn't in the set, or no route object for AS52973 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 | AS52973 in it | Not covered |
|---|---|---|---|---|---|
| AS-52973-GLOBAL | TC | 13 | 2 | 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 32 are in fix.csv.
- Route object: none28
- Route object: RIR4
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 186.216.196.0/24 | No route object for it. A route object for 186.216.192.0/21 with origin AS52973 covers it (filters allowing more-specifics accept it). Add a route object with origin AS52973 in the RIR database for the space. |
| Route object: none | 186.216.204.0/24 | No route object for it. A route object for 186.216.200.0/21 with origin AS52973 covers it (filters allowing more-specifics accept it). Add a route object with origin AS52973 in the RIR database for the space. |
| Route object: none | 186.216.192.0/22 | No route object for it. A route object for 186.216.192.0/21 with origin AS52973 covers it (filters allowing more-specifics accept it). Add a route object with origin AS52973 in the RIR database for the space. |
| Route object: none | 186.216.192.0/23 | No route object for it. A route object for 186.216.192.0/21 with origin AS52973 covers it (filters allowing more-specifics accept it). Add a route object with origin AS52973 in the RIR database for the space. |
| Route object: none | 186.216.194.0/23 | No route object for it. A route object for 186.216.192.0/21 with origin AS52973 covers it (filters allowing more-specifics accept it). Add a route object with origin AS52973 in the RIR database for the space. |
| Route object: none | 186.216.196.0/22 | No route object for it. A route object for 186.216.192.0/21 with origin AS52973 covers it (filters allowing more-specifics accept it). Add a route object with origin AS52973 in the RIR database for the space. |
| Route object: none | 186.216.196.0/23 | No route object for it. A route object for 186.216.192.0/21 with origin AS52973 covers it (filters allowing more-specifics accept it). Add a route object with origin AS52973 in the RIR database for the space. |
| Route object: none | 186.216.198.0/23 | No route object for it. A route object for 186.216.192.0/21 with origin AS52973 covers it (filters allowing more-specifics accept it). Add a route object with origin AS52973 in the RIR database for the space. |
| Route object: none | 186.216.200.0/22 | No route object for it. A route object for 186.216.200.0/21 with origin AS52973 covers it (filters allowing more-specifics accept it). Add a route object with origin AS52973 in the RIR database for the space. |
| Route object: none | 186.216.200.0/23 | No route object for it. A route object for 186.216.200.0/21 with origin AS52973 covers it (filters allowing more-specifics accept it). Add a route object with origin AS52973 in the RIR database for the space. |
| Route object: none | 186.216.202.0/23 | No route object for it. A route object for 186.216.200.0/21 with origin AS52973 covers it (filters allowing more-specifics accept it). Add a route object with origin AS52973 in the RIR database for the space. |
| Route object: none | 186.216.204.0/22 | No route object for it. A route object for 186.216.200.0/21 with origin AS52973 covers it (filters allowing more-specifics accept it). Add a route object with origin AS52973 in the RIR database for the space. |
| Route object: none | 186.216.204.0/23 | No route object for it. A route object for 186.216.200.0/21 with origin AS52973 covers it (filters allowing more-specifics accept it). Add a route object with origin AS52973 in the RIR database for the space. |
| Route object: none | 186.216.206.0/23 | No route object for it. A route object for 186.216.200.0/21 with origin AS52973 covers it (filters allowing more-specifics accept it). Add a route object with origin AS52973 in the RIR database for the space. |
| Route object: none | 186.216.192.0/24 | No route object for it. A route object for 186.216.192.0/21 with origin AS52973 covers it (filters allowing more-specifics accept it). Add a route object with origin AS52973 in the RIR database for the space. |
| Route object: none | 186.216.193.0/24 | No route object for it. A route object for 186.216.192.0/21 with origin AS52973 covers it (filters allowing more-specifics accept it). Add a route object with origin AS52973 in the RIR database for the space. |
| Route object: none | 186.216.194.0/24 | No route object for it. A route object for 186.216.192.0/21 with origin AS52973 covers it (filters allowing more-specifics accept it). Add a route object with origin AS52973 in the RIR database for the space. |
| Route object: none | 186.216.195.0/24 | No route object for it. A route object for 186.216.192.0/21 with origin AS52973 covers it (filters allowing more-specifics accept it). Add a route object with origin AS52973 in the RIR database for the space. |
| Route object: none | 186.216.197.0/24 | No route object for it. A route object for 186.216.192.0/21 with origin AS52973 covers it (filters allowing more-specifics accept it). Add a route object with origin AS52973 in the RIR database for the space. |
| Route object: none | 186.216.198.0/24 | No route object for it. A route object for 186.216.192.0/21 with origin AS52973 covers it (filters allowing more-specifics accept it). Add a route object with origin AS52973 in the RIR database for the space. |
| Route object: none | 186.216.199.0/24 | No route object for it. A route object for 186.216.192.0/21 with origin AS52973 covers it (filters allowing more-specifics accept it). Add a route object with origin AS52973 in the RIR database for the space. |
| Route object: none | 186.216.200.0/24 | No route object for it. A route object for 186.216.200.0/21 with origin AS52973 covers it (filters allowing more-specifics accept it). Add a route object with origin AS52973 in the RIR database for the space. |
| Route object: none | 186.216.201.0/24 | No route object for it. A route object for 186.216.200.0/21 with origin AS52973 covers it (filters allowing more-specifics accept it). Add a route object with origin AS52973 in the RIR database for the space. |
| Route object: none | 186.216.202.0/24 | No route object for it. A route object for 186.216.200.0/21 with origin AS52973 covers it (filters allowing more-specifics accept it). Add a route object with origin AS52973 in the RIR database for the space. |
| Route object: none | 186.216.203.0/24 | No route object for it. A route object for 186.216.200.0/21 with origin AS52973 covers it (filters allowing more-specifics accept it). Add a route object with origin AS52973 in the RIR database for the space. |
| Route object: none | 186.216.205.0/24 | No route object for it. A route object for 186.216.200.0/21 with origin AS52973 covers it (filters allowing more-specifics accept it). Add a route object with origin AS52973 in the RIR database for the space. |
| Route object: none | 186.216.206.0/24 | No route object for it. A route object for 186.216.200.0/21 with origin AS52973 covers it (filters allowing more-specifics accept it). Add a route object with origin AS52973 in the RIR database for the space. |
| Route object: none | 186.216.207.0/24 | No route object for it. A route object for 186.216.200.0/21 with origin AS52973 covers it (filters allowing more-specifics accept it). Add a route object with origin AS52973 in the RIR database for the space. |
| Route object: RIR | 186.216.192.0/20 | Route object only in ALTDB, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 186.216.192.0/21 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 186.216.200.0/21 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 2804:3b00::/32 | Route object only in ALTDB, TC. Add it in the RIR database for the space. |
Route objects not announced
Every route object with origin AS52973 is announced.
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.