Skip to main content

AS58648

AT-I-NET

AT-I, Inc.

Registry

Authoritative registration data

AS number
58648
Name
AT-I-NET
Organisation
AT-I, Inc.
Country
Flag of Japan JP Japan
RIR
APNIC
Registered
Source:asn:rdap retrieved

IPv4 prefixes

7

IPv6 prefixes

0

Total announced

7

Announced prefixes

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

Prefixes announced by AS58648
103.30.164.0/22 IPv4 /22 not checked
150.9.252.0/23 IPv4 /23 not checked
103.30.164.0/24 IPv4 /24 not checked
103.30.165.0/24 IPv4 /24 not checked
103.30.166.0/24 IPv4 /24 not checked
103.30.167.0/24 IPv4 /24 not checked
219.100.252.0/24 IPv4 /24 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 AS58648
Address families
JPIX OSAKA 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 AS58648 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

3 networks seen before AS58648 in AS paths

Observed upstreams
Families
AS7529 NETIRD 237 1,565
v4
AS2519 VECTANT 275 549
v4
AS6939 HURRICANE 34 224
v4

No rows match “”.

Showing of

Observed downstreams

0 networks seen after AS58648 in AS paths

No downstreams observed

This AS was not seen carrying traffic towards another network.

Uncertain adjacencies

2 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS35280 F5 1 6
v4
AS59105 1 6
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.