Loading…

AS138311 LIMERICK-AS-IN - Limerick Technologies Pvt Ltd

India · Autonomous System

IPv4 announced

11.5K

0.00 × /8

IPv6 announced

/48 blocks

Prefixes

routed

Country

India

Topology (CAIDA AS Rank)

The network's position in the inter-domain routing hierarchy: its customer cone, connectivity, and transit role.

Customer cone

ASes reachable as customers

AS rank

#3,120

by customer-cone size (1 = largest)

Connectivity

2 providers · 2 peers · 7 customers

Transit role

Transit / access

carries traffic for downstream customers

Upstream providers

Settlement-free peers

Downstream customers

Peering & transit neighbours (CAIDA)

Inferred AS-level relationships: 2 upstream providers, 2 peers and 7 downstream customers. The graph shows the largest few of each; the lists link through.

Upstream providers2

give this network transit

Settlement-free peers2

exchange traffic directly

Downstream customers7

buy transit from it

Relationships are inferred from BGP by CAIDA and refreshed monthly. Transit links are well captured; some private and IXP peering is under-observed, so peer counts are a lower bound.

Routing hygiene & RPKI

How well this network secures and documents its BGP announcements — RPKI origin validation, IRR registration, and an overall hygiene score.

Hygiene score

0–100 · RPKI × IRR × consistency

RPKI coverage

51%

5.9K of 11.5K routed addrs valid

RPKI invalid

no invalid prefixes

IRR registered

44%

27 of 61 prefixes documented

Announcement composition61 routed prefixes

IPv6 deployment

Measured share of this network's users reaching the Internet over IPv6 (APNIC end-user measurement, India).

IPv6 capable

0.5%

users that can reach IPv6-only content

IPv6 preferred

0.1%

users that use IPv6 when both are offered

Capable0.5%

Has working IPv6 connectivity, even if it isn't always chosen.

Preferred0.1%

IPv6 wins when a destination is dual-stacked — the real-world usage rate.

Announced prefixes

Currently announced prefixes, live from RIPEstat.

61 prefixes currently seen by RIPEstat.

103.84.83.0/24103.96.41.0/242405:3440:4::/48103.6.120.0/24103.96.42.0/24103.132.245.0/24103.169.240.0/242405:3440:5::/48103.133.159.0/24103.157.123.0/24103.157.122.0/242405:3440:a::/48103.207.11.0/242405:3440:3::/48103.175.171.0/24103.163.91.0/24103.195.82.0/242405:3440:8::/48103.160.174.0/24103.212.153.0/24103.196.184.0/24103.139.171.0/24103.212.154.0/242405:3440:e::/48103.169.241.0/242405:3440:b::/48103.212.155.0/24103.139.170.0/24103.196.185.0/24103.84.82.0/24103.84.80.0/24202.179.69.0/24210.16.93.0/24103.176.187.0/24103.132.244.0/24103.212.152.0/242405:3440:c::/48103.171.133.0/24103.171.132.0/24103.160.175.0/242405:3440::/482405:3440:1::/48202.6.198.0/242405:3440:9::/482405:3440:6::/48103.195.83.0/24103.175.170.0/24103.239.174.0/24210.16.92.0/24103.84.81.0/24103.176.186.0/24103.96.40.0/242405:3440:d::/482405:3440:2::/48103.163.90.0/242405:3440:7::/48103.6.121.0/24202.6.199.0/242405:3440:f::/48103.239.175.0/24103.133.158.0/24

Fetching announced prefixes from RIPEstat…