Loading…

AS55915 CLASSIC-NP - Classic Tech Pvt. Ltd.

Nepal · Autonomous System

IPv4 announced

14.6K

0.00 × /8

IPv6 announced

66.1K

/48 blocks

Prefixes

routed

Country

Nepal

Interconnection (PeeringDB)

Where this network meets others — public exchange points, colocation facilities, and declared peering capacity.

Internet exchanges

IXPs present

Facilities

colocation facilities

Peering capacity

20 Gbps

aggregate IX port capacity

Network type

Network service provider

Scope: Asia Pacific

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

#4,626

by customer-cone size (1 = largest)

Connectivity

1 providers · 0 peers · 4 customers

Transit role

Transit / access

carries traffic for downstream customers

Upstream providers

Settlement-free peers

Peering & transit neighbours (CAIDA)

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

Upstream providers1

give this network transit

AS136776 CLASSIC-AS-AP - Classic Tech Transit

Settlement-free peers0

exchange traffic directly

None recorded.

Downstream customers4

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

91%

73.5K of 80.7K routed addrs valid

RPKI invalid

no invalid prefixes

IRR registered

39%

22 of 57 prefixes documented

Announcement composition57 routed prefixes

Announced prefixes

Currently announced prefixes, live from RIPEstat.

57 prefixes currently seen by RIPEstat.

2407:5200:54::/48103.51.18.0/242407:5200:401::/48103.192.76.0/242407:5200:200::/4649.236.213.0/242407:5200:1500::/40103.51.16.0/222407:5200:403::/48103.1.94.0/24103.192.78.0/24103.51.16.0/242407:5200:204::/4645.64.161.0/242407:5200:4920::/462407:5200:601::/482407:5200:1200::/4043.231.210.0/242407:5200:205::/482407:5200::/322407:5200:400::/48103.1.93.0/242407:5200:404::/482407:5200:201::/48103.51.19.0/24103.192.79.0/2445.123.220.0/2445.123.223.0/2445.123.222.0/24202.94.66.0/2449.236.212.0/2245.64.160.0/2245.123.221.0/242407:5200:32::/4849.236.212.0/242407:5200:405::/48103.1.92.0/242407:5200:4c::/46103.1.95.0/2445.64.160.0/2445.64.163.0/2445.64.162.0/2443.231.208.0/24103.192.76.0/22103.1.92.0/222407:5200:300::/4843.231.209.0/242407:5200:48::/48103.192.77.0/2443.231.211.0/2449.236.214.0/2443.231.208.0/222407:5200:200::/482407:5200:49::/4845.123.220.0/2249.236.215.0/24103.51.17.0/24

Fetching announced prefixes from RIPEstat…