bgpreport

Network · data from 2026-11-12

AS30221 T3COM - T3 Communications, Inc.

Registry name: T3COM - T3 Communications, Inc., US · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS30221, 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.45.139.0/24 No ROA None 672 100% 67
63.247.145.0/24 Valid RIR databaseARIN 673 100% 67
63.247.152.0/24 Valid RIR databaseARIN 673 100% 67
208.122.112.0/21 Valid RIR databaseARIN 673 100% 67
208.122.120.0/22 Valid RIR databaseARIN 673 100% 67
208.122.121.0/24 Valid RIR databaseARIN 673 100% 67
208.122.124.0/23 Valid RIR databaseARIN 673 100% 67
208.122.126.0/24 Valid RIR databaseARIN 673 100% 67
63.247.144.0/20 Valid RIR databaseARIN 671 100% 68
68.68.200.0/22 Valid RIR databaseARIN 671 100% 68
68.68.206.0/23 Valid RIR databaseARIN 671 100% 68
68.68.208.0/21 Valid RIR databaseARIN 671 100% 68
68.68.216.0/24 Valid RIR databaseARIN 671 100% 68
68.68.218.0/24 Valid RIR databaseARIN 671 100% 68
68.68.220.0/24 Valid RIR databaseARIN 671 100% 68
68.68.192.0/21 Valid RIR databaseARIN 670 100% 68
68.68.196.0/24 Valid RIR databaseARIN 670 100% 68
68.68.198.0/24 Valid RIR databaseARIN 670 100% 68
208.122.112.0/20 Valid RIR databaseARIN 670 100% 68

AS-SET

AS30221 isn't in PeeringDB, where networks name their AS-SET.

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

  • ROA: none1
  • Route object: none1
  • Route object: not announced99
ChangePrefix or setDetailFull-table peers
ROA: none45.45.139.0/24No ROA covers it. Add a ROA for AS30221, maxLength 24.672 of 673
Route object: none45.45.139.0/24No route object for it. Add a route object with origin AS30221 in the RIR database for the space.672 of 673

Route objects not announced

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

63.247.144.0/21ARINValid
63.247.144.0/22ARINValid
63.247.144.0/23ARINValid
63.247.144.0/24ARINValid
63.247.146.0/23ARINValid
63.247.146.0/24ARINValid
63.247.147.0/24ARINValid
63.247.148.0/22ARINValid
63.247.148.0/23ARINValid
63.247.148.0/24ARINValid
63.247.149.0/24ARINValid
63.247.150.0/23ARINValid
63.247.150.0/24ARINValid
63.247.151.0/24ARINValid
63.247.152.0/21ARINValid
63.247.152.0/22ARINValid
63.247.152.0/23ARINValid
63.247.153.0/24ARINValid
63.247.154.0/23ARINValid
63.247.154.0/24ARINValid
63.247.155.0/24ARINValid
63.247.156.0/22ARINValid
63.247.156.0/23ARINValid
63.247.156.0/24ARINValid
63.247.157.0/24ARINValid
63.247.158.0/23ARINValid
63.247.158.0/24ARINValid
63.247.159.0/24ARINValid
65.77.42.0/24RADBNo ROA
65.77.43.0/24RADBNo ROA
65.77.44.0/24RADBNo ROA
65.77.45.0/24RADBNo ROA
68.68.192.0/22ARINValid
68.68.192.0/23ARINValid
68.68.192.0/24ARINValid
68.68.193.0/24ARINValid
68.68.194.0/23ARINValid
68.68.194.0/24ARINValid
68.68.195.0/24ARINValid
68.68.196.0/22ARINValid
68.68.196.0/23ARINValid
68.68.197.0/24ARINValid
68.68.198.0/23ARINValid
68.68.199.0/24ARINValid
68.68.200.0/23ARINValid
68.68.200.0/24ARINValid
68.68.201.0/24ARINValid
68.68.202.0/23ARINValid
68.68.202.0/24ARINValid
68.68.203.0/24ARINValid
68.68.206.0/24ARINValid
68.68.207.0/24ARINValid
68.68.208.0/22ARINValid
68.68.208.0/23ARINValid
68.68.208.0/24ARINValid
68.68.209.0/24ARINValid
68.68.210.0/23ARINValid
68.68.210.0/24ARINValid
68.68.211.0/24ARINValid
68.68.212.0/22ARINValid
68.68.212.0/23ARINValid
68.68.212.0/24ARINValid
68.68.213.0/24ARINValid
68.68.214.0/23ARINValid
68.68.214.0/24ARINValid
68.68.215.0/24ARINValid
207.30.19.0/24RADBNo ROA
207.30.171.0/24RADBNo ROA
207.30.172.0/24RADBNo ROA
207.30.173.0/24RADBNo ROA
208.122.112.0/22ARINValid
208.122.112.0/23ARINValid
208.122.112.0/24ARINValid
208.122.113.0/24ARINValid
208.122.114.0/23ARINValid
208.122.114.0/24ARINValid
208.122.115.0/24ARINValid
208.122.116.0/22ARINValid
208.122.116.0/23ARINValid
208.122.116.0/24ARINValid
208.122.117.0/24ARINValid
208.122.118.0/23ARINValid
208.122.118.0/24ARINValid
208.122.119.0/24ARINValid
208.122.120.0/21ARINValid
208.122.120.0/23ARINValid
208.122.120.0/24ARINValid
208.122.122.0/23ARINValid
208.122.122.0/24ARINValid
208.122.123.0/24ARINValid
208.122.124.0/22ARINValid
208.122.124.0/24ARINValid
208.122.125.0/24ARINValid
208.122.126.0/23ARINValid
208.122.127.0/24ARINValid
209.26.132.0/24RADBNo ROA
209.26.232.0/24RADBNo ROA
216.183.160.0/21ARINInvalid: origin
2001:470:1e2::/48ARINValid

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.