Skip to main content

AS398482

SCHNEIDERS-COMPUTING-LTD

Schneider's Computing Ltd.

Registry

Authoritative registration data

AS number
398482
Name
SCHNEIDERS-COMPUTING-LTD
Organisation
Schneider's Computing Ltd.
Country
—
RIR
ARIN
Registered
Source:asn:rdap retrieved

IPv4 prefixes

2

IPv6 prefixes

0

Total announced

2

Announced prefixes

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

Prefixes announced by AS398482
209.59.255.0/24 IPv4 /24 not checked
23.135.88.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 AS398482
Address families
TorIX 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 AS398482 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

4 networks seen before AS398482 in AS paths

Observed upstreams
Families
AS174 COGENT-174 96 236
v4
AS1299 TWELVE99 97 234
v4
AS6939 HURRICANE 20 42
v4
AS394256 CLOUDSINGULARITY 1 2
v4

No rows match “”.

Showing – of

Observed downstreams

0 networks seen after AS398482 in AS paths

No downstreams observed

This AS was not seen carrying traffic towards another network.

Uncertain adjacencies

6 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS24482 SGGS-AS-AP 1 18
v4
AS835 GOCODEIT-EDGE 1 2
v4
AS22652 FIBRENOIRE-INTERNET 1 2
v4
AS35280 F5 1 2
v4
AS36236 NETACTUATE 1 2
v4
AS49544 i3Dnet 1 2
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.