bgpreport

Network · data from 2026-11-12

AS52869 WEBMAX TECNOLOGIA LTDA.

Registry name: AS52869 - WEBMAX TECNOLOGIA LTDA, BR · PeeringDB

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

Announced routes

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

2804:1734:f001::/48 Valid Nonecovered by 2804:1734:8000::/33 634 100% 67
2804:1734:4000::/41 Valid Nonecovered by 2804:1734::/33 17 3%low visibility 11
2804:1734:f002::/48 Valid Nonecovered by 2804:1734:8000::/33 1 0%low visibility 1
177.128.64.0/21 Valid Other IRR onlyALTDB, RADB, TC 671 100% 67
177.93.184.0/22 Valid Other IRR onlyALTDB, RADB, TC 670 100% 67
2804:1734::/32 Valid Other IRR onlyRADB, TC 632 99% 67
177.93.184.0/23 Valid Other IRR onlyRADB, TC 27 4%low visibility 12
177.93.186.0/23 Valid Other IRR onlyRADB, TC 27 4%low visibility 12
177.128.64.0/22 Valid Other IRR onlyTC 27 4%low visibility 12
177.128.64.0/23 Valid Other IRR onlyRADB, TC 27 4%low visibility 12
177.128.66.0/23 Valid Other IRR onlyRADB, TC 27 4%low visibility 12
177.128.68.0/22 Valid Other IRR onlyTC 27 4%low visibility 12
177.128.68.0/23 Valid Other IRR onlyRADB, TC 27 4%low visibility 12
177.128.70.0/23 Valid Other IRR onlyRADB, TC 27 4%low visibility 12

AS-SET

PeeringDB's irr_as_set for AS52869: AS52869:AS-WEBMAX. 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 (AS52869 isn't in the set, or no route object for AS52869 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 objectsAS52869 in itNot covered
AS52869:AS-WEBMAX TC 2239 Yes 0

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

  • Route object: none3
  • Route object: RIR11
  • Route object: not announced15
ChangePrefix or setDetailFull-table peers
Route object: none2804:1734:f001::/48No route object for it. A route object for 2804:1734:8000::/33 with origin AS52869 covers it (filters allowing more-specifics accept it). Add a route object with origin AS52869 in the RIR database for the space.634 of 636
Route object: none2804:1734:4000::/41No route object for it. A route object for 2804:1734::/33 with origin AS52869 covers it (filters allowing more-specifics accept it). Add a route object with origin AS52869 in the RIR database for the space.17 of 636
Route object: none2804:1734:f002::/48No route object for it. A route object for 2804:1734:8000::/33 with origin AS52869 covers it (filters allowing more-specifics accept it). Add a route object with origin AS52869 in the RIR database for the space.1 of 636
Route object: RIR177.128.64.0/21Route object only in ALTDB, RADB, TC. Add it in the RIR database for the space.671 of 673
Route object: RIR177.93.184.0/22Route object only in ALTDB, RADB, TC. Add it in the RIR database for the space.670 of 673
Route object: RIR2804:1734::/32Route object only in RADB, TC. Add it in the RIR database for the space.632 of 636
Route object: RIR177.93.184.0/23Route object only in RADB, TC. Add it in the RIR database for the space.27 of 673
Route object: RIR177.93.186.0/23Route object only in RADB, TC. Add it in the RIR database for the space.27 of 673
Route object: RIR177.128.64.0/22Route object only in TC. Add it in the RIR database for the space.27 of 673
Route object: RIR177.128.64.0/23Route object only in RADB, TC. Add it in the RIR database for the space.27 of 673
Route object: RIR177.128.66.0/23Route object only in RADB, TC. Add it in the RIR database for the space.27 of 673
Route object: RIR177.128.68.0/22Route object only in TC. Add it in the RIR database for the space.27 of 673
Route object: RIR177.128.68.0/23Route object only in RADB, TC. Add it in the RIR database for the space.27 of 673
Route object: RIR177.128.70.0/23Route object only in RADB, TC. Add it in the RIR database for the space.27 of 673

Route objects not announced

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

177.93.184.0/24RADB, TCValid
177.93.185.0/24RADB, TCValid
177.93.186.0/24RADB, TCValid
177.93.187.0/24RADB, TCValid
177.128.64.0/24RADB, TCValid
177.128.65.0/24RADB, TCValid
177.128.66.0/24RADB, TCValid
177.128.67.0/24RADB, TCValid
177.128.68.0/24RADB, TCValid
177.128.69.0/24RADB, TCValid
177.128.70.0/24RADB, TCValid
177.128.71.0/24RADB, TCValid
2804:1734::/33TCValid
2804:1734:8000::/33TCValid
2804:1734:f003::/48RADBValid

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.