Network · data from 2026-11-12
AS271548 M A S Telecom
Registry name: AS271548 - M A S Telecom, BR · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS271548, 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.
| 181.174.214.0/24 | Valid | Other IRR onlyALTDB | 672 100% |
| 181.174.213.0/24 | Valid | Other IRR onlyALTDB, RADB | 671 100% |
| 181.174.215.0/24 | Valid | Other IRR onlyALTDB | 671 100% |
| 181.174.212.0/24 | Valid | Other IRR onlyALTDB, RADB | 668 99% |
| 2804:7d3c:3000::/36 | Valid | Other IRR onlyALTDB, RADB | 636 100% |
| 2804:7d3c:1000::/36 | Valid | Other IRR onlyALTDB | 635 100% |
| 2804:7d3c:4000::/36 | Valid | Other IRR onlyALTDB | 635 100% |
| 2804:7d3c::/36 | Valid | Other IRR onlyALTDB, RADB | 634 100% |
AS-SET
PeeringDB's irr_as_set for AS271548: AS-271548. 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 (AS271548 isn't in the set, or no route object for AS271548 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 | AS271548 in it | Not covered |
|---|---|---|---|---|---|
| AS-271548 | ALTDB1 member set in no database: AS271548:AS-CUSTOMERS | 1 | 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 14 are in fix.csv.
- Route object: RIR8
- AS-SET: missing member1
- Route object: not announced5
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: RIR | 181.174.214.0/24 | Route object only in ALTDB. Add it in the RIR database for the space. |
| Route object: RIR | 181.174.213.0/24 | Route object only in ALTDB, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 181.174.215.0/24 | Route object only in ALTDB. Add it in the RIR database for the space. |
| Route object: RIR | 181.174.212.0/24 | Route object only in ALTDB, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 2804:7d3c:3000::/36 | Route object only in ALTDB, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 2804:7d3c:1000::/36 | Route object only in ALTDB. Add it in the RIR database for the space. |
| Route object: RIR | 2804:7d3c:4000::/36 | Route object only in ALTDB. Add it in the RIR database for the space. |
| Route object: RIR | 2804:7d3c::/36 | Route object only in ALTDB, RADB. Add it in the RIR database for the space. |
| AS-SET: missing member | AS-271548 | AS-271548 (ALTDB) lists AS271548:AS-CUSTOMERS; no IRR database read has it. |
Route objects not announced
Route objects with origin AS271548 whose prefix no peer sees AS271548 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 181.174.212.0/22 | ALTDB | No ROA |
| 181.174.212.0/23 | ALTDB, RADB | No ROA |
| 181.174.214.0/23 | ALTDB | No ROA |
| 2804:7d3c::/32 | ALTDB | No ROA |
| 2804:7d3c:2000::/36 | ALTDB, RADB | 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.