bgpreport

Network · data from 2026-11-12

AS52777 BR27 Serviços de Tecnologia Ltda

Registry name: AS52777 - BR27 Servicos de Tecnologia Ltda., BR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS52777, 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.
168.196.168.0/23 No ROA Nonecovered by 168.196.168.0/22 5 1%low visibility 4
168.196.170.0/23 No ROA Nonecovered by 168.196.168.0/22 5 1%low visibility 4
168.196.168.0/22 No ROA Other IRR onlyRADB, TC 668 99% 67
2804:b6c::/32 No ROA Other IRR onlyRADB 636 100% 69
2804:b6c:2000::/36 No ROA Other IRR onlyRADB 633 100% 69
2804:b6c:1000::/36 No ROA Other IRR onlyRADB 630 99% 67
168.196.168.0/24 No ROA Other IRR onlyRADB 5 1%low visibility 4
168.196.169.0/24 No ROA Other IRR onlyRADB 5 1%low visibility 4
168.196.170.0/24 No ROA Other IRR onlyRADB 5 1%low visibility 4
168.196.171.0/24 No ROA Other IRR onlyRADB 5 1%low visibility 4

AS-SET

PeeringDB's irr_as_set for AS52777: AS52777:AS-GLOBAL. 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 (AS52777 isn't in the set, or no route object for AS52777 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 objectsAS52777 in itNot covered
AS52777:AS-GLOBAL TC 193235 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 20 are in fix.csv.

  • ROA: none10
  • Route object: none2
  • Route object: RIR8
ChangePrefix or setDetailFull-table peers
ROA: none168.196.168.0/23No ROA covers it. Add a ROA for AS52777, maxLength 23.5 of 673
Route object: none168.196.168.0/23No route object for it. A route object for 168.196.168.0/22 with origin AS52777 covers it (filters allowing more-specifics accept it). Add a route object with origin AS52777 in the RIR database for the space.5 of 673
ROA: none168.196.170.0/23No ROA covers it. Add a ROA for AS52777, maxLength 23.5 of 673
Route object: none168.196.170.0/23No route object for it. A route object for 168.196.168.0/22 with origin AS52777 covers it (filters allowing more-specifics accept it). Add a route object with origin AS52777 in the RIR database for the space.5 of 673
ROA: none168.196.168.0/22No ROA covers it. Add a ROA for AS52777, maxLength 22.668 of 673
Route object: RIR168.196.168.0/22Route object only in RADB, TC. Add it in the RIR database for the space.668 of 673
ROA: none2804:b6c::/32No ROA covers it. Add a ROA for AS52777, maxLength 32.636 of 636
Route object: RIR2804:b6c::/32Route object only in RADB. Add it in the RIR database for the space.636 of 636
ROA: none2804:b6c:2000::/36No ROA covers it. Add a ROA for AS52777, maxLength 36.633 of 636
Route object: RIR2804:b6c:2000::/36Route object only in RADB. Add it in the RIR database for the space.633 of 636
ROA: none2804:b6c:1000::/36No ROA covers it. Add a ROA for AS52777, maxLength 36.630 of 636
Route object: RIR2804:b6c:1000::/36Route object only in RADB. Add it in the RIR database for the space.630 of 636
ROA: none168.196.168.0/24No ROA covers it. Add a ROA for AS52777, maxLength 24.5 of 673
Route object: RIR168.196.168.0/24Route object only in RADB. Add it in the RIR database for the space.5 of 673
ROA: none168.196.169.0/24No ROA covers it. Add a ROA for AS52777, maxLength 24.5 of 673
Route object: RIR168.196.169.0/24Route object only in RADB. Add it in the RIR database for the space.5 of 673
ROA: none168.196.170.0/24No ROA covers it. Add a ROA for AS52777, maxLength 24.5 of 673
Route object: RIR168.196.170.0/24Route object only in RADB. Add it in the RIR database for the space.5 of 673
ROA: none168.196.171.0/24No ROA covers it. Add a ROA for AS52777, maxLength 24.5 of 673
Route object: RIR168.196.171.0/24Route object only in RADB. Add it in the RIR database for the space.5 of 673

Route objects not announced

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