Network · data from 2026-11-12
AS52531 DL INFORMATICA
Registry name: AS52531 - G6 Internet, BR · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS52531, 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.225.216.0/23 | Valid | Nonecovered by 186.225.216.0/22 | 672 100% |
| 186.250.195.0/24 | Valid | Nonecovered by 186.250.194.0/23 | 669 99% |
| 186.250.194.0/24 | Valid | Nonecovered by 186.250.194.0/23 | 667 99% |
| 2804:df4:9000::/40 | Valid | Nonecovered by 2804:df4:8000::/33 | 633 100% |
| 2804:df4:2000::/36 | Valid | Nonecovered by 2804:df4::/33 | 632 99% |
| 2804:df4:b000::/36 | Valid | Nonecovered by 2804:df4:8000::/33 | 632 99% |
| 2804:df4::/36 | Valid | Nonecovered by 2804:df4::/33 | 631 99% |
| 2804:df4:6000::/36 | Valid | Nonecovered by 2804:df4::/33 | 631 99% |
| 2804:df4:7000::/36 | Valid | Nonecovered by 2804:df4::/33 | 10 2%low visibility |
| 170.233.12.0/24 | Valid | Other IRR onlyRADB | 670 100% |
| 170.233.13.0/24 | Valid | Other IRR onlyRADB | 670 100% |
| 170.233.14.0/23 | Valid | Other IRR onlyRADB | 670 100% |
| 186.225.216.0/22 | Valid | Other IRR onlyRADB | 670 100% |
| 186.225.218.0/23 | Valid | Other IRR onlyRADB | 670 100% |
| 186.225.220.0/23 | Valid | Other IRR onlyRADB | 670 100% |
| 186.225.221.0/24 | Valid | Other IRR onlyRADB | 670 100% |
| 186.225.222.0/23 | Valid | Other IRR onlyRADB | 670 100% |
| 170.233.14.0/24 | Valid | Other IRR onlyRADB | 669 99% |
| 170.233.15.0/24 | Valid | Other IRR onlyRADB | 669 99% |
| 186.225.220.0/24 | Valid | Other IRR onlyRADB | 669 99% |
| 2804:df4:8000::/33 | Valid | Other IRR onlyRADB | 633 100% |
| 186.225.217.0/24 | Valid | Other IRR onlyRADB | 206 31% |
| 186.225.218.0/24 | Valid | Other IRR onlyRADB | 206 31% |
| 186.225.219.0/24 | Valid | Other IRR onlyRADB | 206 31% |
| 186.225.222.0/24 | Valid | Other IRR onlyRADB | 206 31% |
| 186.225.223.0/24 | Valid | Other IRR onlyRADB | 206 31% |
| 186.225.216.0/24 | Valid | Other IRR onlyRADB | 205 30% |
| 2804:df4::/33 | Valid | Other IRR onlyRADB | 2 0%low visibility |
AS-SET
PeeringDB's irr_as_set for AS52531: AS52531:AS-DLINFORMATICA. 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 (AS52531 isn't in the set, or no route object for AS52531 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 | AS52531 in it | Not covered |
|---|---|---|---|---|---|
| AS52531:AS-DLINFORMATICA | RADB | 17 | 1 | Yes | 0 |
| NTTCOM (also) | 10 | 1 | 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: none9
- Route object: RIR19
- Route object: not announced4
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 186.225.216.0/23 | No route object for it. A route object for 186.225.216.0/22 with origin AS52531 covers it (filters allowing more-specifics accept it). Add a route object with origin AS52531 in the RIR database for the space. |
| Route object: none | 186.250.195.0/24 | No route object for it. A route object for 186.250.194.0/23 with origin AS52531 covers it (filters allowing more-specifics accept it). Add a route object with origin AS52531 in the RIR database for the space. |
| Route object: none | 186.250.194.0/24 | No route object for it. A route object for 186.250.194.0/23 with origin AS52531 covers it (filters allowing more-specifics accept it). Add a route object with origin AS52531 in the RIR database for the space. |
| Route object: none | 2804:df4:9000::/40 | No route object for it. A route object for 2804:df4:8000::/33 with origin AS52531 covers it (filters allowing more-specifics accept it). Add a route object with origin AS52531 in the RIR database for the space. |
| Route object: none | 2804:df4:2000::/36 | No route object for it. A route object for 2804:df4::/33 with origin AS52531 covers it (filters allowing more-specifics accept it). Add a route object with origin AS52531 in the RIR database for the space. |
| Route object: none | 2804:df4:b000::/36 | No route object for it. A route object for 2804:df4:8000::/33 with origin AS52531 covers it (filters allowing more-specifics accept it). Add a route object with origin AS52531 in the RIR database for the space. |
| Route object: none | 2804:df4::/36 | No route object for it. A route object for 2804:df4::/33 with origin AS52531 covers it (filters allowing more-specifics accept it). Add a route object with origin AS52531 in the RIR database for the space. |
| Route object: none | 2804:df4:6000::/36 | No route object for it. A route object for 2804:df4::/33 with origin AS52531 covers it (filters allowing more-specifics accept it). Add a route object with origin AS52531 in the RIR database for the space. |
| Route object: none | 2804:df4:7000::/36 | No route object for it. A route object for 2804:df4::/33 with origin AS52531 covers it (filters allowing more-specifics accept it). Add a route object with origin AS52531 in the RIR database for the space. |
| Route object: RIR | 170.233.12.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 170.233.13.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 170.233.14.0/23 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 186.225.216.0/22 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 186.225.218.0/23 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 186.225.220.0/23 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 186.225.221.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 186.225.222.0/23 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 170.233.14.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 170.233.15.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 186.225.220.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 2804:df4:8000::/33 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 186.225.217.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 186.225.218.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 186.225.219.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 186.225.222.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 186.225.223.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 186.225.216.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 2804:df4::/33 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS52531 whose prefix no peer sees AS52531 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 170.233.12.0/22 | RADB, TC | Valid |
| 186.225.216.0/21 | TC | Valid |
| 186.250.194.0/23 | RADB | Valid |
| 2804:df4::/32 | TC | 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.