bgpreport

Network · data from 2026-11-12

AS52820 Brasilfone Telecomunicao Ltda

Registry name: AS52820 - Brasilfone S/A, BR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS52820, 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.
200.155.77.112/28 No ROA None 1 0%low visibility 1
177.52.174.0/24 Valid Nonecovered by 177.52.174.0/23 669 99% 67
177.52.175.0/24 Valid Nonecovered by 177.52.174.0/23 667 99% 67
2804:8ac0:8000::/34 Valid Nonecovered by 2804:8ac0::/32 635 100% 67
177.52.174.0/23 Valid Other IRR onlyRADB, TC 669 99% 67
2804:8ac0::/32 Valid Other IRR onlyTC 635 100% 67

AS-SET

PeeringDB's irr_as_set for AS52820: TC::AS-BRASILFONE. 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 (AS52820 isn't in the set, or no route object for AS52820 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 objectsAS52820 in itNot covered
TC::AS-BRASILFONE In no IRR database read today.

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

  • ROA: none1
  • Route object: none4
  • Route object: RIR2
  • AS-SET: not found1
ChangePrefix or setDetailFull-table peers
ROA: none200.155.77.112/28No ROA covers it. Add a ROA for AS52820, maxLength 28.1 of 673
Route object: none200.155.77.112/28No route object for it. Add a route object with origin AS52820 in the RIR database for the space.1 of 673
Route object: none177.52.174.0/24No route object for it. A route object for 177.52.174.0/23 with origin AS52820 covers it (filters allowing more-specifics accept it). Add a route object with origin AS52820 in the RIR database for the space.669 of 673
Route object: none177.52.175.0/24No route object for it. A route object for 177.52.174.0/23 with origin AS52820 covers it (filters allowing more-specifics accept it). Add a route object with origin AS52820 in the RIR database for the space.667 of 673
Route object: none2804:8ac0:8000::/34No route object for it. A route object for 2804:8ac0::/32 with origin AS52820 covers it (filters allowing more-specifics accept it). Add a route object with origin AS52820 in the RIR database for the space.635 of 636
Route object: RIR177.52.174.0/23Route object only in RADB, TC. Add it in the RIR database for the space.669 of 673
Route object: RIR2804:8ac0::/32Route object only in TC. Add it in the RIR database for the space.635 of 636
AS-SET: not foundTC::AS-BRASILFONEPeeringDB names TC::AS-BRASILFONE; no IRR database read has it.

Route objects not announced

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