Network · data from 2026-11-12

AS62467 TXNet Communications

Registry name: TXNET - TXNet Communications LLC, US · PeeringDB

5IPv4 routes 100.0% RPKI valid · 100.0% with a route object

4IPv6 routes 100.0% RPKI valid · 75.0% with a route object

0RPKI invalid 0 origin · 0 maxLength

0No ROA 1 with no route object for this origin

0Low visibility seen by under 10% of full-table peers

5Route objects not announced registered with origin AS62467, seen from no peer

Announced routes

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


2602:fc05:ff::/48	Valid	None	634 100%	70
23.186.248.0/24	Valid	RIR databaseARIN, RADB	671 100%	67
104.167.240.0/24	Valid	RIR databaseARIN	671 100%	67
104.167.243.0/24	Valid	RIR databaseARIN	671 100%	67
204.197.168.0/24	Valid	RIR databaseARIN	671 100%	67
204.197.169.0/24	Valid	RIR databaseARIN	671 100%	67
2602:f83a::/40	Valid	RIR databaseARIN, RADB	634 100%	70
2602:fc13::/48	Valid	RIR databaseARIN	634 100%	69
2602:fccf:800::/37	Valid	RIR databaseARIN	634 100%	70

AS-SET

PeeringDB's irr_as_set for AS62467: ARIN::AS62467:AS-TXNET. 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 (AS62467 isn't in the set, or no route object for AS62467 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.

Name	Database	ASNs	Sets	Route objects	AS62467 in it	Not covered
ARIN::AS62467:AS-TXNET	ARIN2 member sets in no database: AS-IFOG-US, AS-PIPE	17	17	122	Yes	1

Name

Database

ASNs

Sets

Route objects

AS62467 in it

Not covered

ARIN::AS62467:AS-TXNET

ARIN2 member sets in no database: AS-IFOG-US, AS-PIPE

122

Yes

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: none1
AS-SET: missing member2
Route object: not announced5

Change	Prefix or set	Detail	Full-table peers
Route object: none	2602:fc05:ff::/48	No route object for it. Add a route object with origin AS62467 in the RIR database for the space.	634 of 636
AS-SET: missing member	ARIN::AS62467:AS-TXNET	AS62467:AS-TXNET (ARIN) lists AS-IFOG-US; no IRR database read has it.
AS-SET: missing member	ARIN::AS62467:AS-TXNET	AS62467:AS-TXNET (ARIN) lists AS-PIPE; no IRR database read has it.

Change

Prefix or set

Detail

Full-table peers

Route object: none

2602:fc05:ff::/48

No route object for it. Add a route object with origin AS62467 in the RIR database for the space.

634 of 636

AS-SET: missing member

ARIN::AS62467:AS-TXNET

AS62467:AS-TXNET (ARIN) lists AS-IFOG-US; no IRR database read has it.

AS-SET: missing member

ARIN::AS62467:AS-TXNET

AS62467:AS-TXNET (ARIN) lists AS-PIPE; no IRR database read has it.

Route objects not announced

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


44.32.104.0/24	RADB	No ROA
216.109.188.0/24	ARIN	Valid
216.109.189.0/24	ARIN	Valid
216.109.190.0/24	ARIN	Valid
216.109.191.0/24	ARIN	Valid

44.32.104.0/24

RADB

No ROA

216.109.188.0/24

ARIN

Valid

216.109.189.0/24

ARIN

Valid

216.109.190.0/24

ARIN

Valid

216.109.191.0/24

ARIN

Valid

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.