bgpreport

Network · data from 2026-11-12

AS263339 BRASILNET - 3WLINK

Registry name: AS263339 - 3WLINK INTERNET LTDA, BR · PeeringDB

17IPv4 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
0Low visibility seen by under 10% of full-table peers
0Route objects not announced registered with origin AS263339, seen from no peer

Announced routes

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

191.36.192.0/24 Valid Other IRR onlyRADB 669 99% 67
191.36.193.0/24 Valid Other IRR onlyRADB 669 99% 67
191.36.194.0/24 Valid Other IRR onlyRADB 669 99% 67
191.36.195.0/24 Valid Other IRR onlyRADB 669 99% 67
191.36.196.0/24 Valid Other IRR onlyRADB 669 99% 67
191.36.197.0/24 Valid Other IRR onlyRADB 669 99% 67
191.36.199.0/24 Valid Other IRR onlyRADB 669 99% 67
191.36.200.0/24 Valid Other IRR onlyRADB 669 99% 67
191.36.202.0/24 Valid Other IRR onlyRADB 669 99% 67
191.36.203.0/24 Valid Other IRR onlyRADB 669 99% 67
191.36.204.0/24 Valid Other IRR onlyRADB 669 99% 67
191.36.205.0/24 Valid Other IRR onlyRADB 669 99% 67
191.36.206.0/24 Valid Other IRR onlyRADB 669 99% 67
191.36.207.0/24 Valid Other IRR onlyRADB 669 99% 67
191.36.192.0/20 Valid Other IRR onlyRADB 668 99% 67
191.36.198.0/24 Valid Other IRR onlyRADB 668 99% 67
191.36.201.0/24 Valid Other IRR onlyRADB 668 99% 67
2804:1498::/32 Valid Other IRR onlyRADB 636 100% 67
2804:1498::/33 Valid Other IRR onlyRADB 636 100% 67
2804:1498:8000::/33 Valid Other IRR onlyRADB 636 100% 67

AS-SET

PeeringDB's irr_as_set for AS263339: RADB::AS-3WLINK-CDN RADB::AS-3WLINK. 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 (AS263339 isn't in the set, or no route object for AS263339 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 objectsAS263339 in itNot covered
RADB::AS-3WLINK-CDN RADB 2185 Yes 0
RADB::AS-3WLINK 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 21 are in fix.csv.

  • Route object: RIR20
  • AS-SET: not found1
ChangePrefix or setDetailFull-table peers
Route object: RIR191.36.192.0/24Route object only in RADB. Add it in the RIR database for the space.669 of 673
Route object: RIR191.36.193.0/24Route object only in RADB. Add it in the RIR database for the space.669 of 673
Route object: RIR191.36.194.0/24Route object only in RADB. Add it in the RIR database for the space.669 of 673
Route object: RIR191.36.195.0/24Route object only in RADB. Add it in the RIR database for the space.669 of 673
Route object: RIR191.36.196.0/24Route object only in RADB. Add it in the RIR database for the space.669 of 673
Route object: RIR191.36.197.0/24Route object only in RADB. Add it in the RIR database for the space.669 of 673
Route object: RIR191.36.199.0/24Route object only in RADB. Add it in the RIR database for the space.669 of 673
Route object: RIR191.36.200.0/24Route object only in RADB. Add it in the RIR database for the space.669 of 673
Route object: RIR191.36.202.0/24Route object only in RADB. Add it in the RIR database for the space.669 of 673
Route object: RIR191.36.203.0/24Route object only in RADB. Add it in the RIR database for the space.669 of 673
Route object: RIR191.36.204.0/24Route object only in RADB. Add it in the RIR database for the space.669 of 673
Route object: RIR191.36.205.0/24Route object only in RADB. Add it in the RIR database for the space.669 of 673
Route object: RIR191.36.206.0/24Route object only in RADB. Add it in the RIR database for the space.669 of 673
Route object: RIR191.36.207.0/24Route object only in RADB. Add it in the RIR database for the space.669 of 673
Route object: RIR191.36.192.0/20Route object only in RADB. Add it in the RIR database for the space.668 of 673
Route object: RIR191.36.198.0/24Route object only in RADB. Add it in the RIR database for the space.668 of 673
Route object: RIR191.36.201.0/24Route object only in RADB. Add it in the RIR database for the space.668 of 673
Route object: RIR2804:1498::/32Route object only in RADB. Add it in the RIR database for the space.636 of 636
Route object: RIR2804:1498::/33Route object only in RADB. Add it in the RIR database for the space.636 of 636
Route object: RIR2804:1498:8000::/33Route object only in RADB. Add it in the RIR database for the space.636 of 636
AS-SET: not foundRADB::AS-3WLINKPeeringDB names RADB::AS-3WLINK; no IRR database read has it.

Route objects not announced

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