Skip to main content

AS12496

IDNET

IDNet

Registry

Authoritative registration data

AS number
12496
Name
IDNET
Organisation
IDNet
Country
—
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

6

IPv6 prefixes

2

Total announced

8

Announced prefixes

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

Prefixes announced by AS12496
212.69.32.0/19 IPv4 /19 RPKI valid
217.144.80.0/20 IPv4 /20 RPKI valid
91.135.0.0/20 IPv4 /20 RPKI valid
93.89.128.0/20 IPv4 /20 RPKI valid
195.72.33.0/24 IPv4 /24 not checked
91.90.171.0/24 IPv4 /24 not checked
2a02:390::/32 IPv6 /32 not checked
2001:678:b60::/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 AS12496
Address families
LINX LON1: Main 30,000 Mbps IPv4 · IPv6
LINX LON2 30,000 Mbps IPv4 · IPv6
LONAP: LON0 40,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 AS12496 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

46 networks seen before AS12496 in AS paths

No rows match “”.

Showing – of

Observed downstreams

4 networks seen after AS12496 in AS paths

Observed downstreams
Families
AS59617 ANDYD 467 675
v4 v6
AS199385 GNOME 266 341
v4
AS44697 C3-UK 153 193
v4
AS65020 16 18
v6

No rows match “”.

Showing – of

Uncertain adjacencies

39 adjacencies that may be an artefact of collector peering

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.