bgpreport

Network · data from 2026-11-12

AS268707 4WNET AS268707

Registry name: AS268707 - 4W NET ES TELECOMUNICACOES LTDA, BR · PeeringDB

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

Announced routes

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

38.226.3.0/24 No ROA Other IRR onlyRADB 672 100% 66
2804:5984:b001::/48 Valid Nonecovered by 2804:5984:b000::/36 635 100% 67
2804:5984:b002::/48 Valid Nonecovered by 2804:5984:b000::/36 635 100% 67
45.169.160.0/24 Valid Other IRR onlyALTDB, RADB, TC 672 100% 66
45.169.160.0/23 Valid Other IRR onlyRADB, TC 671 100% 66
45.169.161.0/24 Valid Other IRR onlyALTDB, RADB, TC 671 100% 66
2804:5984:8000::/33 Valid Other IRR onlyALTDB, RADB, TC 635 100% 67
2804:5984:8000::/36 Valid Other IRR onlyRADB 635 100% 67
2804:5984:8482::/48 Valid Other IRR onlyRADB 635 100% 67
2804:5984:9000::/36 Valid Other IRR onlyRADB 635 100% 67
2804:5984:a000::/36 Valid Other IRR onlyRADB 635 100% 67
2804:5984:b000::/36 Valid Other IRR onlyRADB 635 100% 67
2804:5984:b000::/48 Valid Other IRR onlyRADB 635 100% 67
2804:5984:a102::/48 Valid Other IRR onlyRADB 634 100% 67
2804:5984:ae00::/40 Valid Other IRR onlyALTDB, TC 634 100% 68
2804:5984:8000::/35 Valid Other IRR onlyRADB 2 0%low visibility 2
104.234.244.0/24 Valid RIR databaseALTDB, ARIN, RADB, TC 671 100% 66
198.242.60.0/24 Valid RIR databaseALTDB, ARIN, TC 671 100% 66

AS-SET

PeeringDB's irr_as_set for AS268707: AS268707:AS-4WNET. 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 (AS268707 isn't in the set, or no route object for AS268707 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 objectsAS268707 in itNot covered
AS268707:AS-4WNET ALTDB 5811,123 Yes 0
TC (also) 010 No 18

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 35 are in fix.csv.

  • ROA: none1
  • Route object: none2
  • Route object: RIR14
  • Route object: not announced18
ChangePrefix or setDetailFull-table peers
ROA: none38.226.3.0/24No ROA covers it. Add a ROA for AS268707, maxLength 24.672 of 673
Route object: RIR38.226.3.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: none2804:5984:b001::/48No route object for it. A route object for 2804:5984:b000::/36 with origin AS268707 covers it (filters allowing more-specifics accept it). Add a route object with origin AS268707 in the RIR database for the space.635 of 636
Route object: none2804:5984:b002::/48No route object for it. A route object for 2804:5984:b000::/36 with origin AS268707 covers it (filters allowing more-specifics accept it). Add a route object with origin AS268707 in the RIR database for the space.635 of 636
Route object: RIR45.169.160.0/24Route object only in ALTDB, RADB, TC. Add it in the RIR database for the space.672 of 673
Route object: RIR45.169.160.0/23Route object only in RADB, TC. Add it in the RIR database for the space.671 of 673
Route object: RIR45.169.161.0/24Route object only in ALTDB, RADB, TC. Add it in the RIR database for the space.671 of 673
Route object: RIR2804:5984:8000::/33Route object only in ALTDB, RADB, TC. Add it in the RIR database for the space.635 of 636
Route object: RIR2804:5984:8000::/36Route object only in RADB. Add it in the RIR database for the space.635 of 636
Route object: RIR2804:5984:8482::/48Route object only in RADB. Add it in the RIR database for the space.635 of 636
Route object: RIR2804:5984:9000::/36Route object only in RADB. Add it in the RIR database for the space.635 of 636
Route object: RIR2804:5984:a000::/36Route object only in RADB. Add it in the RIR database for the space.635 of 636
Route object: RIR2804:5984:b000::/36Route object only in RADB. Add it in the RIR database for the space.635 of 636
Route object: RIR2804:5984:b000::/48Route object only in RADB. Add it in the RIR database for the space.635 of 636
Route object: RIR2804:5984:a102::/48Route object only in RADB. Add it in the RIR database for the space.634 of 636
Route object: RIR2804:5984:ae00::/40Route object only in ALTDB, TC. Add it in the RIR database for the space.634 of 636
Route object: RIR2804:5984:8000::/35Route object only in RADB. Add it in the RIR database for the space.2 of 636

Route objects not announced

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

2804:5984::/32RADB, TCValid
2804:5984::/33ALTDB, RADB, TCValid
2804:5984:8000::/34RADBValid
2804:5984:8400::/42RADBValid
2804:5984:8440::/42RADBValid
2804:5984:8a00::/40RADBValid
2804:5984:8d00::/40ALTDB, RADB, TCValid
2804:5984:a000::/48ALTDB, RADB, TCValid
2804:5984:a001::/48RADBValid
2804:5984:a800::/40RADBValid
2804:5984:a900::/44ALTDB, TCValid
2804:5984:c000::/34RADBValid
2804:5984:c000::/36RADBValid
2804:5984:cade::/48ALTDB, RADB, TCValid
2804:5984:cafe::/48ALTDB, RADB, TCValid
2804:5984:d000::/36RADBValid
2804:5984:e000::/36RADBValid
2804:5984:f000::/36RADBValid

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.