Network · data from 2026-11-12
AS263852 3MDMI
Registry name: AS263852 - 3M DE MAGE INFORMATICA LTDA, BR · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS263852, 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.
| 138.186.43.0/24 | No ROA | Nonecovered by 138.186.42.0/23 | 154 23% |
| 138.186.40.0/22 | No ROA | Other IRR onlyTC | 665 99% |
| 138.186.40.0/23 | No ROA | Other IRR onlyRADB, TC | 149 22% |
AS-SET
PeeringDB's irr_as_set for AS263852: AS263852:AS-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 (AS263852 isn't in the set, or no route object for AS263852 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 | AS263852 in it | Not covered |
|---|---|---|---|---|---|
| AS263852:AS-GLOBAL | TC | 5 | 1 | No | 3 |
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 11 are in fix.csv.
- ROA: none3
- Route object: none1
- Route object: RIR2
- AS-SET: own ASN1
- Route object: not announced4
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 138.186.43.0/24 | No ROA covers it. Add a ROA for AS263852, maxLength 24. |
| Route object: none | 138.186.43.0/24 | No route object for it. A route object for 138.186.42.0/23 with origin AS263852 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263852 in the RIR database for the space. |
| ROA: none | 138.186.40.0/22 | No ROA covers it. Add a ROA for AS263852, maxLength 22. |
| Route object: RIR | 138.186.40.0/22 | Route object only in TC. Add it in the RIR database for the space. |
| ROA: none | 138.186.40.0/23 | No ROA covers it. Add a ROA for AS263852, maxLength 23. |
| Route object: RIR | 138.186.40.0/23 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| AS-SET: own ASN | AS263852:AS-GLOBAL | AS263852 isn't in AS263852:AS-GLOBAL (TC) once expanded. Add AS263852 to it. |
Route objects not announced
Route objects with origin AS263852 whose prefix no peer sees AS263852 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 138.186.40.0/24 | TC | No ROA |
| 138.186.41.0/24 | TC | No ROA |
| 138.186.42.0/23 | RADB | No ROA |
| 2804:26b8::/32 | RADB, 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.