Skip to main content

AS6140

TWO-P

Two P

Registry

Authoritative registration data

AS number
6140
Name
TWO-P
Organisation
Two P
Country
—
RIR
ARIN
Registered
Source:asn:rdap retrieved

IPv4 prefixes

8

IPv6 prefixes

1

Total announced

9

Announced prefixes

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

Prefixes announced by AS6140
107.161.208.0/20 IPv4 /20 RPKI valid
44.2.52.0/23 IPv4 /23 RPKI not found
192.203.228.0/24 IPv4 /24 RPKI not found
198.182.225.0/24 IPv4 /24 not checked
216.41.142.0/24 IPv4 /24 RPKI valid
44.31.197.0/24 IPv4 /24 not checked
44.31.70.0/24 IPv4 /24 not checked
44.4.59.0/24 IPv4 /24 not checked
2602:ffd3::/36 IPv6 /36 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 AS6140
Address families
ARIX: Primary 10,000 Mbps IPv4 · IPv6
FCIX 10,000 Mbps IPv4 · IPv6
FREMIX 10,000 Mbps IPv4 · IPv6
SFMIX 10,000 Mbps IPv4 · IPv6
TahoeIX: Peering 1,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 AS6140 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

4 networks seen before AS6140 in AS paths

Observed upstreams
Families
AS6939 HURRICANE 158 1,628
v4 v6
AS1299 TWELVE99 162 1,304
v4 v6
AS40271 SFMIX-TRANSIT 1 27
v4 v6
AS58057 SECUREBIT 1 1
v6

No rows match “”.

Showing – of

Observed downstreams

1 networks seen after AS6140 in AS paths

Observed downstreams
Families
AS22296 VORSK 31 171
v4 v6

No rows match “”.

Showing – of

Uncertain adjacencies

3 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS49544 i3Dnet 2 14
v4 v6
AS924 CLOUDIE 2 12
v4 v6
AS36236 NETACTUATE 2 11
v4 v6

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.