Skip to main content

AS42310

IEDR

---- Heanet ----

Registry

Authoritative registration data

AS number
42310
Name
IEDR
Organisation
---- Heanet ----
Country
—
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

6

IPv6 prefixes

3

Total announced

9

Announced prefixes

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

Prefixes announced by AS42310
77.72.72.0/23 IPv4 /23 RPKI valid
77.72.74.0/23 IPv4 /23 RPKI valid
77.72.76.0/23 IPv4 /23 RPKI valid
77.72.78.0/23 IPv4 /23 RPKI valid
77.72.78.0/24 IPv4 /24 not checked
77.72.79.0/24 IPv4 /24 RPKI valid
2a01:4b0:1::/48 IPv6 /48 not checked
2a01:4b0:2::/48 IPv6 /48 not checked
2a01:4b0::/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 AS42310
Address families
INEX LAN1: INEX LAN1 1,000 Mbps IPv4 · IPv6
INEX LAN2 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 AS42310 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

9 networks seen before AS42310 in AS paths

Observed upstreams
Families
AS207044 ENET-AS 201 661
v4 v6
AS1213 Asiera 205 615
v4 v6
AS8220 COLT 80 155
v4 v6
AS6939 HURRICANE 41 68
v4 v6
AS6461 ZAYO-6461 6 15
v4 v6
AS9002 RETN-AS 6 8
v6
AS3303 SWISSCOM 3 8
v4 v6
AS4455 BSO 1 2
v4
AS6204 ZET-NET 1 2
v4

No rows match “”.

Showing – of

Observed downstreams

1 networks seen after AS42310 in AS paths

Observed downstreams
Families
AS1921 RCODEZERO-ANYCAST-SEC1-TLD 3 3
v4

No rows match “”.

Showing – of

Uncertain adjacencies

1 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS13237 LAMBDANET-AS 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.