Skip to main content

AS48099

VIAIP-AS

ViaIP LLC

Registry

Authoritative registration data

AS number
48099
Name
VIAIP-AS
Organisation
ViaIP LLC
Country
—
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

1

IPv6 prefixes

0

Total announced

1

Announced prefixes

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

Prefixes announced by AS48099
91.213.176.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

No Internet Exchange memberships found

The exchange directory has no current membership records for this AS.

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

Source:ripestat:asn-neighbours observed

Observed upstreams

6 networks seen before AS48099 in AS paths

Observed upstreams
Families
AS43727 KVANT-TELECOM 148 203
v4
AS47692 NESSUS 2 4
v4
AS25091 IP-Max 2 2
v4
AS6204 ZET-NET 1 1
v4
AS6663 TTI-NET 1 1
v4
AS39351 ESAB-AS 1 1
v4

No rows match “”.

Showing – of

Observed downstreams

1 networks seen after AS48099 in AS paths

Observed downstreams
Families
AS58096 Elit-TV-AS 3 32
v4

No rows match “”.

Showing – of

Uncertain adjacencies

7 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS8218 NEO-ASN 1 2
v4
AS24482 SGGS-AS-AP 1 2
v4
AS37721 ORG-VTS1-AFRINIC 1 1
v4
AS49673 TRUENETWORK 1 1
v4
AS200612 GulfBridgeInternational 1 1
v4
AS205112 PHILUNET 1 1
v4
AS208972 1 1
v4

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.