Skip to main content

AS40080

AS-IRLTOOLKIT

IRLToolkit Inc.

Registry

Authoritative registration data

AS number
40080
Name
AS-IRLTOOLKIT
Organisation
IRLToolkit Inc.
Country
—
RIR
ARIN
Registered
Source:asn:rdap retrieved

IPv4 prefixes

5

IPv6 prefixes

3

Total announced

8

Announced prefixes

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

Prefixes announced by AS40080
205.147.203.0/24 IPv4 /24 not checked
205.207.28.0/24 IPv4 /24 not checked
205.207.66.0/24 IPv4 /24 not checked
40.27.14.0/24 IPv4 /24 not checked
40.27.15.0/24 IPv4 /24 not checked
2602:fb31:1::/48 IPv6 /48 not checked
2602:fb31:2::/48 IPv6 /48 not checked
2602:fb31::/48 IPv6 /48 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 AS40080
Address families
Any2West 10,000 Mbps IPv4 · IPv6
Equinix Ashburn 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 AS40080 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

1 networks seen before AS40080 in AS paths

Observed upstreams
Families
AS137409 GSLNETWORKS-AS-AP 419 2,846
v4 v6

No rows match “”.

Showing – of

Observed downstreams

0 networks seen after AS40080 in AS paths

No downstreams observed

This AS was not seen carrying traffic towards another network.

Uncertain adjacencies

1 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS49544 i3Dnet 1 7
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.