bgpreport

Network · data from 2026-11-12

AS266445 SEA TELECOM AS266445

Registry name: AS266445 - SEA TELECOM LTDA, BR · PeeringDB

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

Announced routes

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

149.102.65.0/24 No ROA Nonecovered by 149.102.64.0/19 671 100% 66
149.102.64.0/24 No ROA Nonecovered by 149.102.64.0/19 669 99% 67
149.102.67.0/24 No ROA Nonecovered by 149.102.64.0/19 669 99% 67
149.102.85.0/24 No ROA Nonecovered by 149.102.64.0/19 210 31% 56
149.102.64.0/19 No ROA Other IRR onlyRADB 672 100% 66
149.102.81.0/24 No ROA Other IRR onlyRADB 672 100% 67
149.102.83.0/24 No ROA Other IRR onlyRADB 210 31% 56
170.82.180.0/22 Valid Other IRR onlyTC 673 100% 66
170.82.180.0/24 Valid Other IRR onlyTC 673 100% 66
170.82.181.0/24 Valid Other IRR onlyTC 673 100% 66
170.82.182.0/24 Valid Other IRR onlyTC 672 100% 66
170.82.183.0/24 Valid Other IRR onlyTC 672 100% 66
2804:37f0:ab::/48 Valid Other IRR onlyTC 636 100% 67
2804:37f0::/32 Valid Other IRR onlyTC 633 100% 67
2804:37f0:af::/48 Valid Other IRR onlyTC 631 99% 67
2804:37f0:ac::/48 Valid Other IRR onlyTC 605 95% 67

AS-SET

PeeringDB's irr_as_set for AS266445: AS266445 AS-SEA. 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 (AS266445 isn't in the set, or no route object for AS266445 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 objectsAS266445 in itNot covered
AS266445 A single AS number, not a set: AS266445 (this network), 57 route objects.
AS-SEA TC 13314,334 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 68 are in fix.csv.

  • ROA: none7
  • Route object: none4
  • Route object: RIR12
  • Route object: not announced45
ChangePrefix or setDetailFull-table peers
ROA: none149.102.65.0/24No ROA covers it. Add a ROA for AS266445, maxLength 24.671 of 673
Route object: none149.102.65.0/24No route object for it. A route object for 149.102.64.0/19 with origin AS266445 covers it (filters allowing more-specifics accept it). Add a route object with origin AS266445 in the RIR database for the space.671 of 673
ROA: none149.102.64.0/24No ROA covers it. Add a ROA for AS266445, maxLength 24.669 of 673
Route object: none149.102.64.0/24No route object for it. A route object for 149.102.64.0/19 with origin AS266445 covers it (filters allowing more-specifics accept it). Add a route object with origin AS266445 in the RIR database for the space.669 of 673
ROA: none149.102.67.0/24No ROA covers it. Add a ROA for AS266445, maxLength 24.669 of 673
Route object: none149.102.67.0/24No route object for it. A route object for 149.102.64.0/19 with origin AS266445 covers it (filters allowing more-specifics accept it). Add a route object with origin AS266445 in the RIR database for the space.669 of 673
ROA: none149.102.85.0/24No ROA covers it. Add a ROA for AS266445, maxLength 24.210 of 673
Route object: none149.102.85.0/24No route object for it. A route object for 149.102.64.0/19 with origin AS266445 covers it (filters allowing more-specifics accept it). Add a route object with origin AS266445 in the RIR database for the space.210 of 673
ROA: none149.102.64.0/19No ROA covers it. Add a ROA for AS266445, maxLength 19.672 of 673
Route object: RIR149.102.64.0/19Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none149.102.81.0/24No ROA covers it. Add a ROA for AS266445, maxLength 24.672 of 673
Route object: RIR149.102.81.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none149.102.83.0/24No ROA covers it. Add a ROA for AS266445, maxLength 24.210 of 673
Route object: RIR149.102.83.0/24Route object only in RADB. Add it in the RIR database for the space.210 of 673
Route object: RIR170.82.180.0/22Route object only in TC. Add it in the RIR database for the space.673 of 673
Route object: RIR170.82.180.0/24Route object only in TC. Add it in the RIR database for the space.673 of 673
Route object: RIR170.82.181.0/24Route object only in TC. Add it in the RIR database for the space.673 of 673
Route object: RIR170.82.182.0/24Route object only in TC. Add it in the RIR database for the space.672 of 673
Route object: RIR170.82.183.0/24Route object only in TC. Add it in the RIR database for the space.672 of 673
Route object: RIR2804:37f0:ab::/48Route object only in TC. Add it in the RIR database for the space.636 of 636
Route object: RIR2804:37f0::/32Route object only in TC. Add it in the RIR database for the space.633 of 636
Route object: RIR2804:37f0:af::/48Route object only in TC. Add it in the RIR database for the space.631 of 636
Route object: RIR2804:37f0:ac::/48Route object only in TC. Add it in the RIR database for the space.605 of 636

Route objects not announced

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

149.102.76.0/24RADBNo ROA
149.102.77.0/24RADBNo ROA
149.102.78.0/24RADBNo ROA
149.102.79.0/24RADBNo ROA
149.102.80.0/24RADBNo ROA
149.102.82.0/24RADBNo ROA
170.82.180.0/23TCValid
170.82.182.0/23TCValid
2804:37f0::/40TCValid
2804:37f0:a8::/48TCValid
2804:37f0:a9::/48TCValid
2804:37f0:aa::/48TCValid
2804:37f0:ad::/48TCValid
2804:37f0:ae::/48TCValid
2804:37f0:1000::/40TCValid
2804:37f0:1800::/40TCValid
2804:37f0:2000::/40TCValid
2804:37f0:2800::/40TCValid
2804:37f0:3000::/40TCValid
2804:37f0:3800::/40TCValid
2804:37f0:4000::/40TCValid
2804:37f0:4800::/40TCValid
2804:37f0:5000::/40TCValid
2804:37f0:5800::/40TCValid
2804:37f0:6000::/40TCValid
2804:37f0:6800::/40TCValid
2804:37f0:7000::/40TCValid
2804:37f0:7800::/40TCValid
2804:37f0:8000::/40TCValid
2804:37f0:8400::/40TCValid
2804:37f0:8800::/40TCValid
2804:37f0:9000::/40TCValid
2804:37f0:9800::/40TCValid
2804:37f0:a000::/40TCValid
2804:37f0:a800::/40TCValid
2804:37f0:b000::/40TCValid
2804:37f0:b800::/40TCValid
2804:37f0:c000::/40TCValid
2804:37f0:c800::/40TCValid
2804:37f0:d000::/40TCValid
2804:37f0:d800::/40TCValid
2804:37f0:e000::/40TCValid
2804:37f0:e800::/40TCValid
2804:37f0:f000::/40TCValid
2804:37f0:f800::/40TCValid

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.