bgpreport

Network · data from 2026-11-12

AS272209 Real Fibra Telecom LTDA

Registry name: AS272209 - Real Fibra Telecom LTDA, BR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS272209, 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.
2804:83a0::/33 No ROA Nonecovered by 2804:83a0::/32 353 56% 65
2804:83a0:8000::/33 No ROA Nonecovered by 2804:83a0::/32 353 56% 65
2804:83a0::/32 No ROA Other IRR onlyALTDB 636 100% 67

AS-SET

PeeringDB's irr_as_set for AS272209: AS-272209. 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 (AS272209 isn't in the set, or no route object for AS272209 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 objectsAS272209 in itNot covered
AS-272209 ALTDB1 member set in no database: AS272209:AS-CUSTOMERS 111 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 7 are in fix.csv.

  • ROA: none3
  • Route object: none2
  • Route object: RIR1
  • AS-SET: missing member1
ChangePrefix or setDetailFull-table peers
ROA: none2804:83a0::/33No ROA covers it. Add a ROA for AS272209, maxLength 33.353 of 636
Route object: none2804:83a0::/33No route object for it. A route object for 2804:83a0::/32 with origin AS272209 covers it (filters allowing more-specifics accept it). Add a route object with origin AS272209 in the RIR database for the space.353 of 636
ROA: none2804:83a0:8000::/33No ROA covers it. Add a ROA for AS272209, maxLength 33.353 of 636
Route object: none2804:83a0:8000::/33No route object for it. A route object for 2804:83a0::/32 with origin AS272209 covers it (filters allowing more-specifics accept it). Add a route object with origin AS272209 in the RIR database for the space.353 of 636
ROA: none2804:83a0::/32No ROA covers it. Add a ROA for AS272209, maxLength 32.636 of 636
Route object: RIR2804:83a0::/32Route object only in ALTDB. Add it in the RIR database for the space.636 of 636
AS-SET: missing memberAS-272209AS-272209 (ALTDB) lists AS272209:AS-CUSTOMERS; no IRR database read has it.

Route objects not announced

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