bgpreport

Network · data from 2026-11-12

AS266409 SECW TELECOM

Registry name: AS266409 - SECW TELECOM, BR · PeeringDB

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

Announced routes

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

170.81.68.0/23 Valid Nonecovered by 170.81.68.0/22 672 100% 66
170.81.68.0/24 Valid Nonecovered by 170.81.68.0/22 672 100% 66
170.81.69.0/24 Valid Nonecovered by 170.81.68.0/22 670 100% 67
170.81.70.0/23 Valid Nonecovered by 170.81.68.0/22 669 99% 67
170.81.70.0/24 Valid Nonecovered by 170.81.68.0/22 668 99% 67
2804:3764:40::/44 Valid Nonecovered by 2804:3764::/32 631 99% 67
2804:3764:100::/48 Valid Nonecovered by 2804:3764::/32 631 99% 67
2804:3764:1a70::/44 Valid Nonecovered by 2804:3764::/32 631 99% 67
2804:3764:1a80::/44 Valid Nonecovered by 2804:3764::/32 631 99% 67
2804:3764:8039::/48 Valid Nonecovered by 2804:3764::/32 631 99% 67
2804:3764:803a::/48 Valid Nonecovered by 2804:3764::/32 631 99% 67
2804:3764:e000::/48 Valid Nonecovered by 2804:3764::/32 631 99% 67
2804:3764:e001::/48 Valid Nonecovered by 2804:3764::/32 631 99% 67
2804:3764:fffa::/48 Valid Nonecovered by 2804:3764::/32 631 99% 67
2804:3764:fffd::/48 Valid Nonecovered by 2804:3764::/32 631 99% 67
2804:3764:500::/48 Valid Nonecovered by 2804:3764::/32 306 48% 62
170.81.68.0/22 Valid Other IRR onlyRADB 671 100% 66
200.15.10.0/23 Valid Other IRR onlyALTDB 669 99% 66
2804:3764::/32 Valid Other IRR onlyRADB 631 99% 67

AS-SET

PeeringDB's irr_as_set for AS266409: AS-SECW. 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 (AS266409 isn't in the set, or no route object for AS266409 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 objectsAS266409 in itNot covered
AS-SECW ALTDB1 member set in no database: AS-CMA 1882125,345 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 20 are in fix.csv.

  • Route object: none16
  • Route object: RIR3
  • AS-SET: missing member1
ChangePrefix or setDetailFull-table peers
Route object: none170.81.68.0/23No route object for it. A route object for 170.81.68.0/22 with origin AS266409 covers it (filters allowing more-specifics accept it). Add a route object with origin AS266409 in the RIR database for the space.672 of 673
Route object: none170.81.68.0/24No route object for it. A route object for 170.81.68.0/22 with origin AS266409 covers it (filters allowing more-specifics accept it). Add a route object with origin AS266409 in the RIR database for the space.672 of 673
Route object: none170.81.69.0/24No route object for it. A route object for 170.81.68.0/22 with origin AS266409 covers it (filters allowing more-specifics accept it). Add a route object with origin AS266409 in the RIR database for the space.670 of 673
Route object: none170.81.70.0/23No route object for it. A route object for 170.81.68.0/22 with origin AS266409 covers it (filters allowing more-specifics accept it). Add a route object with origin AS266409 in the RIR database for the space.669 of 673
Route object: none170.81.70.0/24No route object for it. A route object for 170.81.68.0/22 with origin AS266409 covers it (filters allowing more-specifics accept it). Add a route object with origin AS266409 in the RIR database for the space.668 of 673
Route object: none2804:3764:40::/44No route object for it. A route object for 2804:3764::/32 with origin AS266409 covers it (filters allowing more-specifics accept it). Add a route object with origin AS266409 in the RIR database for the space.631 of 636
Route object: none2804:3764:100::/48No route object for it. A route object for 2804:3764::/32 with origin AS266409 covers it (filters allowing more-specifics accept it). Add a route object with origin AS266409 in the RIR database for the space.631 of 636
Route object: none2804:3764:1a70::/44No route object for it. A route object for 2804:3764::/32 with origin AS266409 covers it (filters allowing more-specifics accept it). Add a route object with origin AS266409 in the RIR database for the space.631 of 636
Route object: none2804:3764:1a80::/44No route object for it. A route object for 2804:3764::/32 with origin AS266409 covers it (filters allowing more-specifics accept it). Add a route object with origin AS266409 in the RIR database for the space.631 of 636
Route object: none2804:3764:8039::/48No route object for it. A route object for 2804:3764::/32 with origin AS266409 covers it (filters allowing more-specifics accept it). Add a route object with origin AS266409 in the RIR database for the space.631 of 636
Route object: none2804:3764:803a::/48No route object for it. A route object for 2804:3764::/32 with origin AS266409 covers it (filters allowing more-specifics accept it). Add a route object with origin AS266409 in the RIR database for the space.631 of 636
Route object: none2804:3764:e000::/48No route object for it. A route object for 2804:3764::/32 with origin AS266409 covers it (filters allowing more-specifics accept it). Add a route object with origin AS266409 in the RIR database for the space.631 of 636
Route object: none2804:3764:e001::/48No route object for it. A route object for 2804:3764::/32 with origin AS266409 covers it (filters allowing more-specifics accept it). Add a route object with origin AS266409 in the RIR database for the space.631 of 636
Route object: none2804:3764:fffa::/48No route object for it. A route object for 2804:3764::/32 with origin AS266409 covers it (filters allowing more-specifics accept it). Add a route object with origin AS266409 in the RIR database for the space.631 of 636
Route object: none2804:3764:fffd::/48No route object for it. A route object for 2804:3764::/32 with origin AS266409 covers it (filters allowing more-specifics accept it). Add a route object with origin AS266409 in the RIR database for the space.631 of 636
Route object: none2804:3764:500::/48No route object for it. A route object for 2804:3764::/32 with origin AS266409 covers it (filters allowing more-specifics accept it). Add a route object with origin AS266409 in the RIR database for the space.306 of 636
Route object: RIR170.81.68.0/22Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR200.15.10.0/23Route object only in ALTDB. Add it in the RIR database for the space.669 of 673
Route object: RIR2804:3764::/32Route object only in RADB. Add it in the RIR database for the space.631 of 636
AS-SET: missing memberAS-SECWAS-SECW (ALTDB) lists AS-CMA; no IRR database read has it.

Route objects not announced

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