bgpreport

Network · data from 2026-11-12

AS61776 Provedor de Acesso a Internet EIRELI

Registry name: AS61776 - Provedor de Acesso a Internet Eireli, BR · PeeringDB

12IPv4 routes 91.7% RPKI valid · 75.0% with a route object
6IPv6 routes 100.0% RPKI valid · 66.7% with a route object
0RPKI invalid 0 origin · 0 maxLength
1No ROA 5 with no route object for this origin
2Low visibility seen by under 10% of full-table peers
14Route objects not announced registered with origin AS61776, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS61776, 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.
186.231.31.32/29 No ROA None 3 0%low visibility 3
177.53.136.0/24 Valid Nonecovered by 177.53.136.0/22 672 100% 67
177.53.138.0/23 Valid Nonecovered by 177.53.136.0/22 672 100% 67
2804:192c:4000::/36 Valid Nonecovered by 2804:192c::/32 635 100% 67
2804:192c:f800::/38 Valid Nonecovered by 2804:192c::/32 635 100% 67
143.208.136.0/22 Valid Other IRR onlyALTDB, RADB, TC 669 99% 67
177.53.137.0/24 Valid Other IRR onlyRADB 669 99% 67
200.196.138.0/24 Valid Other IRR onlyRADB 668 99% 67
200.196.136.0/24 Valid Other IRR onlyRADB 667 99% 67
177.53.139.0/24 Valid Other IRR onlyRADB 666 99% 67
200.196.138.0/23 Valid Other IRR onlyRADB 665 99% 67
200.196.139.0/24 Valid Other IRR onlyRADB 665 99% 67
200.196.137.0/24 Valid Other IRR onlyRADB 661 98% 67
2804:192c:3000::/36 Valid Other IRR onlyRADB 635 100% 69
2804:192c:7000::/36 Valid Other IRR onlyRADB 635 100% 69
2804:192c::/36 Valid Other IRR onlyRADB 634 100% 69
2804:192c:2000::/36 Valid Other IRR onlyRADB 631 99% 69
177.53.136.0/22 Valid Other IRR onlyRADB, TC 1 0%low visibility 1

AS-SET

PeeringDB's irr_as_set for AS61776: TC::AS61776. 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 (AS61776 isn't in the set, or no route object for AS61776 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 objectsAS61776 in itNot covered
TC::AS61776 A single AS number, not a set: AS61776 (this network), 27 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 33 are in fix.csv.

  • ROA: none1
  • Route object: none5
  • Route object: RIR13
  • Route object: not announced14
ChangePrefix or setDetailFull-table peers
ROA: none186.231.31.32/29No ROA covers it. Add a ROA for AS61776, maxLength 29.3 of 673
Route object: none186.231.31.32/29No route object for it. Add a route object with origin AS61776 in the RIR database for the space.3 of 673
Route object: none177.53.136.0/24No route object for it. A route object for 177.53.136.0/22 with origin AS61776 covers it (filters allowing more-specifics accept it). Add a route object with origin AS61776 in the RIR database for the space.672 of 673
Route object: none177.53.138.0/23No route object for it. A route object for 177.53.136.0/22 with origin AS61776 covers it (filters allowing more-specifics accept it). Add a route object with origin AS61776 in the RIR database for the space.672 of 673
Route object: none2804:192c:4000::/36No route object for it. A route object for 2804:192c::/32 with origin AS61776 covers it (filters allowing more-specifics accept it). Add a route object with origin AS61776 in the RIR database for the space.635 of 636
Route object: none2804:192c:f800::/38No route object for it. A route object for 2804:192c::/32 with origin AS61776 covers it (filters allowing more-specifics accept it). Add a route object with origin AS61776 in the RIR database for the space.635 of 636
Route object: RIR143.208.136.0/22Route object only in ALTDB, RADB, TC. Add it in the RIR database for the space.669 of 673
Route object: RIR177.53.137.0/24Route object only in RADB. Add it in the RIR database for the space.669 of 673
Route object: RIR200.196.138.0/24Route object only in RADB. Add it in the RIR database for the space.668 of 673
Route object: RIR200.196.136.0/24Route object only in RADB. Add it in the RIR database for the space.667 of 673
Route object: RIR177.53.139.0/24Route object only in RADB. Add it in the RIR database for the space.666 of 673
Route object: RIR200.196.138.0/23Route object only in RADB. Add it in the RIR database for the space.665 of 673
Route object: RIR200.196.139.0/24Route object only in RADB. Add it in the RIR database for the space.665 of 673
Route object: RIR200.196.137.0/24Route object only in RADB. Add it in the RIR database for the space.661 of 673
Route object: RIR2804:192c:3000::/36Route object only in RADB. Add it in the RIR database for the space.635 of 636
Route object: RIR2804:192c:7000::/36Route object only in RADB. Add it in the RIR database for the space.635 of 636
Route object: RIR2804:192c::/36Route object only in RADB. Add it in the RIR database for the space.634 of 636
Route object: RIR2804:192c:2000::/36Route object only in RADB. Add it in the RIR database for the space.631 of 636
Route object: RIR177.53.136.0/22Route object only in RADB, TC. Add it in the RIR database for the space.1 of 673

Route objects not announced

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

143.208.136.0/23RADBValid
143.208.136.0/24RADBValid
143.208.137.0/24RADBValid
143.208.138.0/23RADBValid
143.208.138.0/24RADBValid
143.208.139.0/24RADBValid
200.196.136.0/22ALTDB, RADB, TCValid
200.196.136.0/23RADBValid
2804:192c::/32ALTDB, RADB, TCValid
2804:192c:800::/38RADBValid
2804:192c:2000::/37RADBValid
2804:192c:2800::/37RADBValid
2804:192c:2906::/48RADBValid
2804:44dc::/32RADBNo 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.