Skip to main content

AS146924

VICTORY-AS-IN

VICTORY DIGITAL NETWORK PRIVATE LIMITED

Registry

Authoritative registration data

AS number
146924
Name
VICTORY-AS-IN
Organisation
VICTORY DIGITAL NETWORK PRIVATE LIMITED
Country
Flag of India IN India
RIR
APNIC
Registered
Source:asn:rdap retrieved

IPv4 prefixes

2

IPv6 prefixes

1

Total announced

3

Announced prefixes

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

Prefixes announced by AS146924
103.171.202.0/24 IPv4 /24 not checked
103.171.203.0/24 IPv4 /24 not checked
2400:54e0::/32 IPv6 /32 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 AS146924
Address families
DE-CIX Mumbai: DE-CIX Mumbai Peering LAN 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 AS146924 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

1 networks seen before AS146924 in AS paths

Observed upstreams
Families
AS9730 269 708
v4

No rows match “”.

Showing of

Observed downstreams

0 networks seen after AS146924 in AS paths

No downstreams observed

This AS was not seen carrying traffic towards another network.

Uncertain adjacencies

4 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS36236 NETACTUATE 2 3
v4 v6
AS45489 SLT-GLOBAL 2 3
v4 v6
AS142289 2 3
v4 v6
AS24482 SGGS-AS-AP 1 1
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.