bgpreport

Network · data from 2026-11-12

AS266148 MAIS FIBRA TELECOMUNICACAO LTDA

Registry name: AS266148 - MAIS FIBRA TELECOMUNICACAO LTDA, BR · PeeringDB

7IPv4 routes 100.0% RPKI valid · 100.0% with a route object
7IPv6 routes 100.0% RPKI valid · 100.0% with a route object
0RPKI invalid 0 origin · 0 maxLength
0No ROA 0 with no route object for this origin
12Low visibility seen by under 10% of full-table peers
0Route objects not announced registered with origin AS266148, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS266148, 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.
201.140.236.0/22 Valid Other IRR onlyTC 665 99% 67
2804:3b6c::/32 Valid Other IRR onlyTC 635 100% 67
201.140.236.0/23 Valid Other IRR onlyTC 30 4%low visibility 11
201.140.238.0/23 Valid Other IRR onlyTC 30 4%low visibility 11
2804:3b6c::/33 Valid Other IRR onlyTC 29 5%low visibility 12
2804:3b6c:8000::/33 Valid Other IRR onlyTC 29 5%low visibility 12
201.140.236.0/24 Valid Other IRR onlyTC 1 0%low visibility 1
201.140.237.0/24 Valid Other IRR onlyTC 1 0%low visibility 1
201.140.238.0/24 Valid Other IRR onlyTC 1 0%low visibility 1
201.140.239.0/24 Valid Other IRR onlyTC 1 0%low visibility 1
2804:3b6c::/34 Valid Other IRR onlyTC 1 0%low visibility 1
2804:3b6c:4000::/34 Valid Other IRR onlyTC 1 0%low visibility 1
2804:3b6c:8000::/34 Valid Other IRR onlyTC 1 0%low visibility 1
2804:3b6c:c000::/34 Valid Other IRR onlyTC 1 0%low visibility 1

AS-SET

PeeringDB's irr_as_set for AS266148: AS266148:AS-ANNOUNCEMENTS. 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 (AS266148 isn't in the set, or no route object for AS266148 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.

NameDatabaseASNsSets Route objectsAS266148 in itNot covered
AS266148:AS-ANNOUNCEMENTS TC 1114 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: RIR14
ChangePrefix or setDetailFull-table peers
Route object: RIR201.140.236.0/22Route object only in TC. Add it in the RIR database for the space.665 of 673
Route object: RIR2804:3b6c::/32Route object only in TC. Add it in the RIR database for the space.635 of 636
Route object: RIR201.140.236.0/23Route object only in TC. Add it in the RIR database for the space.30 of 673
Route object: RIR201.140.238.0/23Route object only in TC. Add it in the RIR database for the space.30 of 673
Route object: RIR2804:3b6c::/33Route object only in TC. Add it in the RIR database for the space.29 of 636
Route object: RIR2804:3b6c:8000::/33Route object only in TC. Add it in the RIR database for the space.29 of 636
Route object: RIR201.140.236.0/24Route object only in TC. Add it in the RIR database for the space.1 of 673
Route object: RIR201.140.237.0/24Route object only in TC. Add it in the RIR database for the space.1 of 673
Route object: RIR201.140.238.0/24Route object only in TC. Add it in the RIR database for the space.1 of 673
Route object: RIR201.140.239.0/24Route object only in TC. Add it in the RIR database for the space.1 of 673
Route object: RIR2804:3b6c::/34Route object only in TC. Add it in the RIR database for the space.1 of 636
Route object: RIR2804:3b6c:4000::/34Route object only in TC. Add it in the RIR database for the space.1 of 636
Route object: RIR2804:3b6c:8000::/34Route object only in TC. Add it in the RIR database for the space.1 of 636
Route object: RIR2804:3b6c:c000::/34Route object only in TC. Add it in the RIR database for the space.1 of 636

Route objects not announced

Every route object with origin AS266148 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.