bgpreport

Network · data from 2026-11-12

AS267199 RedeMetro Telecom

Registry name: AS267199 - REDEMETRO TELECOMUNICACOES LTDA, BR · PeeringDB

3IPv4 routes 0.0% RPKI valid · 33.3% with a route object
3IPv6 routes 0.0% RPKI valid · 33.3% with a route object
0RPKI invalid 0 origin · 0 maxLength
6No ROA 4 with no route object for this origin
3Low visibility seen by under 10% of full-table peers
0Route objects not announced registered with origin AS267199, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS267199, 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.
45.231.142.0/23 No ROA Nonecovered by 45.231.140.0/22 671 100% 66
45.231.140.0/23 No ROA Nonecovered by 45.231.140.0/22 19 3%low visibility 10
2804:49b8::/33 No ROA Nonecovered by 2804:49b8::/32 9 1%low visibility 7
2804:49b8:8000::/33 No ROA Nonecovered by 2804:49b8::/32 9 1%low visibility 7
45.231.140.0/22 No ROA Other IRR onlyRADB, TC 672 100% 66
2804:49b8::/32 No ROA Other IRR onlyRADB, TC 634 100% 67

AS-SET

PeeringDB's irr_as_set for AS267199: AS267199. 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 (AS267199 isn't in the set, or no route object for AS267199 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 objectsAS267199 in itNot covered
AS267199 A single AS number, not a set: AS267199 (this network), 2 route objects.

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 12 are in fix.csv.

  • ROA: none6
  • Route object: none4
  • Route object: RIR2
ChangePrefix or setDetailFull-table peers
ROA: none45.231.142.0/23No ROA covers it. Add a ROA for AS267199, maxLength 23.671 of 673
Route object: none45.231.142.0/23No route object for it. A route object for 45.231.140.0/22 with origin AS267199 covers it (filters allowing more-specifics accept it). Add a route object with origin AS267199 in the RIR database for the space.671 of 673
ROA: none45.231.140.0/23No ROA covers it. Add a ROA for AS267199, maxLength 23.19 of 673
Route object: none45.231.140.0/23No route object for it. A route object for 45.231.140.0/22 with origin AS267199 covers it (filters allowing more-specifics accept it). Add a route object with origin AS267199 in the RIR database for the space.19 of 673
ROA: none2804:49b8::/33No ROA covers it. Add a ROA for AS267199, maxLength 33.9 of 636
Route object: none2804:49b8::/33No route object for it. A route object for 2804:49b8::/32 with origin AS267199 covers it (filters allowing more-specifics accept it). Add a route object with origin AS267199 in the RIR database for the space.9 of 636
ROA: none2804:49b8:8000::/33No ROA covers it. Add a ROA for AS267199, maxLength 33.9 of 636
Route object: none2804:49b8:8000::/33No route object for it. A route object for 2804:49b8::/32 with origin AS267199 covers it (filters allowing more-specifics accept it). Add a route object with origin AS267199 in the RIR database for the space.9 of 636
ROA: none45.231.140.0/22No ROA covers it. Add a ROA for AS267199, maxLength 22.672 of 673
Route object: RIR45.231.140.0/22Route object only in RADB, TC. Add it in the RIR database for the space.672 of 673
ROA: none2804:49b8::/32No ROA covers it. Add a ROA for AS267199, maxLength 32.634 of 636
Route object: RIR2804:49b8::/32Route object only in RADB, TC. Add it in the RIR database for the space.634 of 636

Route objects not announced

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