Skip to main content

AS12998

BGNET-AS

************************************************************************

Registry

Authoritative registration data

AS number
12998
Name
BGNET-AS
Organisation
************************************************************************
Country
—
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

4

IPv6 prefixes

0

Total announced

4

Announced prefixes

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

Prefixes announced by AS12998
195.3.156.0/22 IPv4 /22 not checked
5.183.200.0/22 IPv4 /22 not checked
91.196.100.0/22 IPv4 /22 not checked
193.227.206.0/23 IPv4 /23 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 AS12998 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

5 networks seen before AS12998 in AS paths

Observed upstreams
Families
AS13249 ITS-UA 425 832
v4
AS48648 KYIVLINK 27 124
v4
AS6939 HURRICANE 20 50
v4
AS14840 ASN14840 4 20
v4
AS6663 TTI-NET 2 5
v4

No rows match “”.

Showing – of

Observed downstreams

3 networks seen after AS12998 in AS paths

Observed downstreams
Families
AS38931 CorsideGroup 151 170
v4
AS48560 VICORD-UA-AS 143 166
v4
AS41485 URDISC-AS 37 41
v4

No rows match “”.

Showing – of

Uncertain adjacencies

3 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS24482 SGGS-AS-AP 2 20
v4
AS48919 UA-CITY-AS 2 5
v4
AS49544 i3Dnet 2 5
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.