Skip to main content

AS154715

CVACCESS-AS-AP

Cvaccess Network And Data Solution

Registry

Authoritative registration data

AS number
154715
Name
CVACCESS-AS-AP
Organisation
Cvaccess Network And Data Solution
Country
Flag of Philippines PH Philippines
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 AS154715
162.4.246.0/24 IPv4 /24 not checked
162.4.247.0/24 IPv4 /24 not checked
2402:6460::/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 AS154715
Address families
BBIX Manila 10,000 Mbps IPv4 · IPv6
GetaFIX Manila: Main 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 AS154715 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

3 networks seen before AS154715 in AS paths

Observed upstreams
Families
AS135423 479 975
v4 v6
AS63927 RISE-HK 29 102
v4
AS135607 29 55
v4 v6

No rows match “”.

Showing – of

Observed downstreams

0 networks seen after AS154715 in AS paths

No downstreams observed

This AS was not seen carrying traffic towards another network.

Uncertain adjacencies

3 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS24482 SGGS-AS-AP 1 3
v4 v6
AS59105 1 3
v4 v6
AS17639 CONVERGE-AS 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.