Skip to main content

AS26088

INLANDTELEPHONE

Inland Internet

Registry

Authoritative registration data

AS number
26088
Name
INLANDTELEPHONE
Organisation
Inland Internet
Country
—
RIR
ARIN
Registered
Source:asn:rdap retrieved

IPv4 prefixes

4

IPv6 prefixes

0

Total announced

4

Announced prefixes

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

Prefixes announced by AS26088
204.106.232.0/21 IPv4 /21 not checked
204.14.96.0/21 IPv4 /21 not checked
185.162.240.0/22 IPv4 /22 not checked
209.209.16.0/22 IPv4 /22 not checked

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 AS26088
Address families
SIX Seattle: MTU 1500 10,000 Mbps IPv4

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 AS26088 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

3 networks seen before AS26088 in AS paths

Observed upstreams
Families
AS6939 HURRICANE 142 720
v4
AS209 CENTURYLINK-US-LEGACY-QWEST 8 36
v4
AS394256 CLOUDSINGULARITY 1 4
v4

No rows match “”.

Showing – of

Observed downstreams

0 networks seen after AS26088 in AS paths

No downstreams observed

This AS was not seen carrying traffic towards another network.

Uncertain adjacencies

4 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS24482 SGGS-AS-AP 1 12
v4
AS9002 RETN-AS 1 4
v4
AS35280 F5 1 4
v4
AS49544 i3Dnet 1 4
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.