bgpreport

Network · data from 2026-11-12

AS53003 EVOLUNET PROVEDORA DE INTERNET

Registry name: AS53003 - EVOLUNET PROVEDORA DE INTERNET LTDA PE, BR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS53003, 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.

177.55.128.0/20 Valid Other IRR onlyRADB, TC 668 99% 66
2804:5038::/32 Valid Other IRR onlyRADB, TC 631 99% 67
177.55.128.0/21 Valid Other IRR onlyRADB, TC 8 1%low visibility 5
177.55.136.0/21 Valid Other IRR onlyRADB, TC 8 1%low visibility 5
2804:5038::/33 Valid Other IRR onlyTC 8 1%low visibility 5
2804:5038:8000::/33 Valid Other IRR onlyTC 8 1%low visibility 5

AS-SET

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

  • Route object: RIR6
  • Route object: not announced22
ChangePrefix or setDetailFull-table peers
Route object: RIR177.55.128.0/20Route object only in RADB, TC. Add it in the RIR database for the space.668 of 673
Route object: RIR2804:5038::/32Route object only in RADB, TC. Add it in the RIR database for the space.631 of 636
Route object: RIR177.55.128.0/21Route object only in RADB, TC. Add it in the RIR database for the space.8 of 673
Route object: RIR177.55.136.0/21Route object only in RADB, TC. Add it in the RIR database for the space.8 of 673
Route object: RIR2804:5038::/33Route object only in TC. Add it in the RIR database for the space.8 of 636
Route object: RIR2804:5038:8000::/33Route object only in TC. Add it in the RIR database for the space.8 of 636

Route objects not announced

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

177.55.128.0/24TCValid
177.55.129.0/24TCValid
177.55.130.0/24RADB, TCValid
177.55.131.0/24TCValid
177.55.132.0/22RADBValid
177.55.132.0/24RADB, TCValid
177.55.133.0/24RADB, TCValid
177.55.134.0/24RADB, TCValid
177.55.135.0/24RADB, TCValid
177.55.136.0/24RADB, TCValid
177.55.137.0/24RADB, TCValid
177.55.138.0/24RADB, TCValid
177.55.139.0/24RADB, TCValid
177.55.140.0/24TCValid
177.55.141.0/24RADB, TCValid
177.55.142.0/24TCValid
177.55.143.0/24RADB, TCValid
2804:5038::/34TCValid
2804:5038::/35RADBValid
2804:5038:4000::/34TCValid
2804:5038:8000::/34TCValid
2804:5038:c000::/34TCValid

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.