Skip to main content

AS134078

NETPLUZ-AS-AP

NETPLUZ HOLDINGS PRIVATE LIMITED

Registry

Authoritative registration data

AS number
134078
Name
NETPLUZ-AS-AP
Organisation
NETPLUZ HOLDINGS PRIVATE LIMITED
Country
Flag of Singapore SG Singapore
RIR
APNIC
Registered
Source:asn:rdap retrieved

IPv4 prefixes

42

IPv6 prefixes

2

Total announced

44

Announced prefixes

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

Prefixes announced by AS134078
202.52.64.0/19 IPv4 /19 RPKI valid
61.14.64.0/19 IPv4 /19 RPKI valid
202.136.16.0/20 IPv4 /20 RPKI valid
202.148.160.0/20 IPv4 /20 not checked
202.52.96.0/20 IPv4 /20 not checked
61.16.0.0/20 IPv4 /20 not checked
203.149.184.0/21 IPv4 /21 RPKI valid
61.13.16.0/21 IPv4 /21 RPKI valid
61.13.24.0/21 IPv4 /21 not checked
61.13.32.0/21 IPv4 /21 not checked
103.227.88.0/22 IPv4 /22 RPKI valid
103.250.56.0/22 IPv4 /22 not checked
103.51.160.0/22 IPv4 /22 RPKI valid
202.52.100.0/22 IPv4 /22 RPKI valid
202.52.104.0/22 IPv4 /22 not checked
202.52.96.0/22 IPv4 /22 RPKI valid
203.149.140.0/22 IPv4 /22 RPKI valid
203.149.168.0/22 IPv4 /22 not checked
45.112.76.0/22 IPv4 /22 not checked
61.13.128.0/22 IPv4 /22 RPKI valid
61.13.132.0/22 IPv4 /22 not checked
61.13.136.0/22 IPv4 /22 RPKI not found
61.16.16.0/22 IPv4 /22 RPKI valid
61.16.32.0/22 IPv4 /22 RPKI valid
61.13.0.0/23 IPv4 /23 RPKI valid
103.234.84.0/24 IPv4 /24 RPKI not found
103.234.85.0/24 IPv4 /24 not checked
103.234.86.0/24 IPv4 /24 RPKI not found
103.234.87.0/24 IPv4 /24 RPKI not found
103.250.58.0/24 IPv4 /24 RPKI valid
103.51.160.0/24 IPv4 /24 not checked
203.149.128.0/24 IPv4 /24 not checked
203.31.234.0/24 IPv4 /24 RPKI valid
61.13.0.0/24 IPv4 /24 RPKI valid
61.13.1.0/24 IPv4 /24 not checked
61.13.132.0/24 IPv4 /24 not checked
61.13.133.0/24 IPv4 /24 not checked
61.13.134.0/24 IPv4 /24 not checked
61.13.135.0/24 IPv4 /24 not checked
61.13.2.0/24 IPv4 /24 not checked
61.14.90.0/24 IPv4 /24 RPKI valid
61.14.95.0/24 IPv4 /24 not checked
2404:1100::/32 IPv6 /32 RPKI valid
2001:df6:ed00::/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 AS134078
Address families
SGIX: Peering LAN 10,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 AS134078 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

10 networks seen before AS134078 in AS paths

Observed upstreams
Families
AS24482 SGGS-AS-AP 628 11,330
v4 v6
AS7473 SINGTEL-AS-AP 749 4,286
v4 v6
AS4657 STARHUB-INTERNET 364 1,612
v4 v6
AS45474 NEXUSGUARD-AS-AP 365 555
v4
AS35280 F5 8 68
v4 v6
AS55518 SGIX-SG 4 12
v4
AS137409 GSLNETWORKS-AS-AP 2 6
v4
AS64049 RJIPL-SG 1 6
v4
AS9304 HUTCHISON-AS-AP 1 3
v4
AS9930 TTNET-MY 1 3
v4

No rows match “”.

Showing – of

Observed downstreams

7 networks seen after AS134078 in AS paths

Observed downstreams
Families
AS134148 SINGAREN-GIX-AS-AP-2 213 1,108
v4
AS23856 SPTEL-AS-AP 131 692
v4 v6
AS4657 STARHUB-INTERNET 53 302
v4
AS17547 M1NET-SG-AP 109 247
v4
AS24482 SGGS-AS-AP 117 188
v4
AS136557 HOST-AS-AP 52 162
v4
AS133535 ALAGASNETWORK-AS-AP 106 148
v4

No rows match “”.

Showing – of

Uncertain adjacencies

7 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS18106 VIEWQWEST-SG-AP 1 35
v4 v6
AS37989 DCS1PTELTD-AS-AP 1 35
v4 v6
AS38001 NEWMEDIAEXPRESS-AS-AP 1 35
v4 v6
AS49544 i3Dnet 1 35
v4 v6
AS133210 ENTECHNOLOGIES-AS-AP 1 35
v4 v6
AS199524 GCORE 1 34
v4
AS17639 CONVERGE-AS 1 5
v4 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.