Skip to main content

AS396431

T38FAX-ASN-1

T38Fax Incorporated

Registry

Authoritative registration data

AS number
396431
Name
T38FAX-ASN-1
Organisation
T38Fax Incorporated
Country
—
RIR
ARIN
Registered
Source:asn:rdap retrieved

IPv4 prefixes

6

IPv6 prefixes

3

Total announced

9

Announced prefixes

Observed in BGP by route collectors, not a registry allocation list

Prefixes announced by AS396431
130.51.64.0/22 IPv4 /22 RPKI valid
130.51.64.0/24 IPv4 /24 RPKI valid
130.51.65.0/24 IPv4 /24 RPKI valid
130.51.66.0/24 IPv4 /24 not checked
8.20.91.0/24 IPv4 /24 RPKI not found
8.9.39.0/24 IPv4 /24 RPKI not found
2620:53:a000::/48 IPv6 /48 RPKI valid
2620:53:a002::/48 IPv6 /48 RPKI valid
2620:53:a00a::/48 IPv6 /48 RPKI valid

No rows match “”.

Showing – of

Source:ripestat:announced-prefixes observed

Internet Exchanges

Exchanges where this network has a listed peering LAN connection

Internet Exchange memberships listed for AS396431
Address families
Equinix Chicago 10,000 Mbps IPv4 · IPv6
PhillyIX 10,000 Mbps IPv4 · IPv6

No rows match “”.

Showing – of

Source:peeringdb retrieved

Exchange membership means the network has a listed connection; it does not prove peering with other members.

Observed adjacencies

Networks seen next to AS396431 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

5 networks seen before AS396431 in AS paths

Observed upstreams
Families
AS1299 TWELVE99 265 1,285
v4 v6
AS6939 HURRICANE 397 1,233
v4 v6
AS2914 NTT-DATA-2914 130 650
v4 v6
AS3356 LEVEL3 76 212
v4 v6
AS8220 COLT 6 32
v4

No rows match “”.

Showing – of

Observed downstreams

1 networks seen after AS396431 in AS paths

Observed downstreams
Families
AS7324 IFAX-ASN-1 385 1,037
v4 v6

No rows match “”.

Showing – of

Uncertain adjacencies

5 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS24482 SGGS-AS-AP 2 90
v4 v6
AS36236 NETACTUATE 2 12
v4 v6
AS49544 i3Dnet 2 12
v4 v6
AS852 ASN852 2 9
v4
AS35280 F5 2 9
v4

No rows match “”.

Showing – of

Note:
These are observed adjacencies derived from BGP path data, not confirmed commercial relationships. A network appearing before another in an AS path does not establish that it is a paying transit customer, a settlement free peer, or anything else contractual. Adjacencies marked uncertain were seen only as direct peers of a route collector, so the collector's own peering may have created them.