bgpreport

Network · data from 2026-11-12

AS28621 NetOeste Telecomunicações Ltda

Registry name: AS28621 - NetOeste Telecomunicacoes Ltda, BR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS28621, 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.
131.0.184.0/22 No ROA Other IRR onlyNTTCOM 672 100% 66
177.128.236.0/22 No ROA Other IRR onlyNTTCOM, RADB 672 100% 66
2804:1ad0::/32 No ROA Other IRR onlyRADB 636 100% 67

AS-SET

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

  • ROA: none3
  • Route object: RIR3
  • AS-SET: not found1
ChangePrefix or setDetailFull-table peers
ROA: none131.0.184.0/22No ROA covers it. Add a ROA for AS28621, maxLength 22.672 of 673
Route object: RIR131.0.184.0/22Route object only in NTTCOM. Add it in the RIR database for the space.672 of 673
ROA: none177.128.236.0/22No ROA covers it. Add a ROA for AS28621, maxLength 22.672 of 673
Route object: RIR177.128.236.0/22Route object only in NTTCOM, RADB. Add it in the RIR database for the space.672 of 673
ROA: none2804:1ad0::/32No ROA covers it. Add a ROA for AS28621, maxLength 32.636 of 636
Route object: RIR2804:1ad0::/32Route object only in RADB. Add it in the RIR database for the space.636 of 636
AS-SET: not foundAS-NETOESTEPeeringDB names AS-NETOESTE; no IRR database read has it.

Route objects not announced

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