Skip to main content

AS134363

EZIT-AS-AP

EZIT Solutions Pte Ltd

Registry

Authoritative registration data

AS number
134363
Name
EZIT-AS-AP
Organisation
EZIT Solutions Pte Ltd
Country
Flag of Singapore SG Singapore
RIR
APNIC
Registered
Source:asn:rdap retrieved

IPv4 prefixes

3

IPv6 prefixes

0

Total announced

3

Announced prefixes

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

Prefixes announced by AS134363
103.61.192.0/23 IPv4 /23 not checked
103.61.192.0/24 IPv4 /24 not checked
103.61.193.0/24 IPv4 /24 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 AS134363
Address families
Equinix Singapore 10,000 Mbps IPv4

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 AS134363 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

9 networks seen before AS134363 in AS paths

Observed upstreams
Families
AS56300 474 595
v4
AS6939 HURRICANE 40 133
v4
AS8966 Etisalat-AS 8 22
v4
AS33891 CORE-BACKBONE 7 18
v4
AS9583 SIFY-AS-IN 1 6
v4
AS137409 GSLNETWORKS-AS-AP 2 5
v4
AS9505 TWGATE-AP 1 2
v4
AS15802 DU-AS1 1 2
v4
AS17557 PKTELECOM-AS-PK 1 2
v4

No rows match “”.

Showing of

Observed downstreams

1 networks seen after AS134363 in AS paths

Observed downstreams
Families
AS133391 267 334
v4

No rows match “”.

Showing of

Uncertain adjacencies

16 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.