bgpreport

Network · data from 2026-11-12

AS53185 Zago & Zago Telecom

Registry name: AS53185 - zago & zago telecomunicacoes ltda, BR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS53185, 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:3f54:100::/41 Invalid: maxLength Nonecovered by 2804:3f54:100::/40 90 14% 43
2804:3f54:180::/41 Invalid: maxLength Nonecovered by 2804:3f54:100::/40 90 14% 43
2804:3f54:1ff::/48 Invalid: maxLength Nonecovered by 2804:3f54:100::/40 90 14% 43
186.227.80.0/22 Valid Other IRR onlyRADB, TC 671 100% 66
186.227.80.0/24 Valid Other IRR onlyRADB, TC 671 100% 66
186.227.82.0/24 Valid Other IRR onlyRADB, TC 671 100% 66
186.227.81.0/24 Valid Other IRR onlyRADB, TC 667 99% 66
186.227.83.0/24 Valid Other IRR onlyRADB, TC 667 99% 67
2804:3f54:100::/40 Valid Other IRR onlyRADB 635 100% 67

AS-SET

PeeringDB's irr_as_set for AS53185: AS53185: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 (AS53185 isn't in the set, or no route object for AS53185 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 objectsAS53185 in itNot covered
AS53185:AS-ANNOUNCEMENTS 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 17 are in fix.csv.

  • ROA: maxLength3
  • Route object: none3
  • Route object: RIR6
  • AS-SET: not found1
  • Route object: not announced4
ChangePrefix or setDetailFull-table peers
ROA: maxLength2804:3f54:100::/41ROA 2804:3f54:100::/40 AS53185 has maxLength 40; the route is a /41. Raise the maxLength, or add a ROA for 2804:3f54:100::/41.90 of 636
Route object: none2804:3f54:100::/41No route object for it. A route object for 2804:3f54:100::/40 with origin AS53185 covers it (filters allowing more-specifics accept it). Add a route object with origin AS53185 in the RIR database for the space.90 of 636
ROA: maxLength2804:3f54:180::/41ROA 2804:3f54:100::/40 AS53185 has maxLength 40; the route is a /41. Raise the maxLength, or add a ROA for 2804:3f54:180::/41.90 of 636
Route object: none2804:3f54:180::/41No route object for it. A route object for 2804:3f54:100::/40 with origin AS53185 covers it (filters allowing more-specifics accept it). Add a route object with origin AS53185 in the RIR database for the space.90 of 636
ROA: maxLength2804:3f54:1ff::/48ROA 2804:3f54:100::/40 AS53185 has maxLength 40; the route is a /48. Raise the maxLength, or add a ROA for 2804:3f54:1ff::/48.90 of 636
Route object: none2804:3f54:1ff::/48No route object for it. A route object for 2804:3f54:100::/40 with origin AS53185 covers it (filters allowing more-specifics accept it). Add a route object with origin AS53185 in the RIR database for the space.90 of 636
Route object: RIR186.227.80.0/22Route object only in RADB, TC. Add it in the RIR database for the space.671 of 673
Route object: RIR186.227.80.0/24Route object only in RADB, TC. Add it in the RIR database for the space.671 of 673
Route object: RIR186.227.82.0/24Route object only in RADB, TC. Add it in the RIR database for the space.671 of 673
Route object: RIR186.227.81.0/24Route object only in RADB, TC. Add it in the RIR database for the space.667 of 673
Route object: RIR186.227.83.0/24Route object only in RADB, TC. Add it in the RIR database for the space.667 of 673
Route object: RIR2804:3f54:100::/40Route object only in RADB. Add it in the RIR database for the space.635 of 636
AS-SET: not foundAS53185:AS-ANNOUNCEMENTSPeeringDB names AS53185:AS-ANNOUNCEMENTS; no IRR database read has it.

Route objects not announced

Route objects with origin AS53185 whose prefix no peer sees AS53185 announce. Many are kept on purpose (backup routes, space announced only in some places).

186.227.80.0/20RADBNo ROA
186.227.80.0/23RADB, TCValid
186.227.82.0/23RADB, TCValid
186.227.89.0/24RADBNo ROA

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.