bgpreport

Network · data from 2026-11-12

AS268210 WB TELECOM

Registry name: AS268210 - WB TELECOM LTDA ME, BR · PeeringDB

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

Announced routes

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

45.236.6.0/24 Valid Nonecovered by 45.236.4.0/22 671 100% 66
45.236.7.0/24 Valid Nonecovered by 45.236.4.0/22 670 100% 66
45.236.4.0/24 Valid Nonecovered by 45.236.4.0/22 667 99% 66
45.236.5.0/24 Valid Nonecovered by 45.236.4.0/22 667 99% 66
45.236.4.0/23 Valid Nonecovered by 45.236.4.0/22 198 29% 54
45.236.6.0/23 Valid Nonecovered by 45.236.4.0/22 198 29% 54
45.236.4.0/22 Valid Other IRR onlyRADB, TC 672 100% 66
2804:4da4::/32 Valid Other IRR onlyRADB, TC 634 100% 67

AS-SET

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

  • Route object: none6
  • Route object: RIR2
ChangePrefix or setDetailFull-table peers
Route object: none45.236.6.0/24No route object for it. A route object for 45.236.4.0/22 with origin AS268210 covers it (filters allowing more-specifics accept it). Add a route object with origin AS268210 in the RIR database for the space.671 of 673
Route object: none45.236.7.0/24No route object for it. A route object for 45.236.4.0/22 with origin AS268210 covers it (filters allowing more-specifics accept it). Add a route object with origin AS268210 in the RIR database for the space.670 of 673
Route object: none45.236.4.0/24No route object for it. A route object for 45.236.4.0/22 with origin AS268210 covers it (filters allowing more-specifics accept it). Add a route object with origin AS268210 in the RIR database for the space.667 of 673
Route object: none45.236.5.0/24No route object for it. A route object for 45.236.4.0/22 with origin AS268210 covers it (filters allowing more-specifics accept it). Add a route object with origin AS268210 in the RIR database for the space.667 of 673
Route object: none45.236.4.0/23No route object for it. A route object for 45.236.4.0/22 with origin AS268210 covers it (filters allowing more-specifics accept it). Add a route object with origin AS268210 in the RIR database for the space.198 of 673
Route object: none45.236.6.0/23No route object for it. A route object for 45.236.4.0/22 with origin AS268210 covers it (filters allowing more-specifics accept it). Add a route object with origin AS268210 in the RIR database for the space.198 of 673
Route object: RIR45.236.4.0/22Route object only in RADB, TC. Add it in the RIR database for the space.672 of 673
Route object: RIR2804:4da4::/32Route object only in RADB, TC. Add it in the RIR database for the space.634 of 636

Route objects not announced

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