Skip to content
KynexBGP

AS49933

Alexander Karl

Germany (DE)

AS49933 peers and adjacencies

Public data cannot confirm who AS49933 has a BGP session with. This page shows three different kinds of evidence, kept separate on purpose.

Upstreams (inferred)

ASNameRelationshipEvidenceLast observed
AS29670IN-BERLIN-AS Individual Network Berlin ("IN-Berlin") e.V.Upstream (inferred)RouteViews paths, RIPEstat inference · 171 paths
AS8298IPNG IPng Networks GmbHUpstream (inferred)RIPEstat inference—
AS25091IP-Max IP-Max SAUpstream (inferred)RIPEstat inference—
AS34549MEER-AS meerfarbig GmbH & Co. KGUpstream (inferred)RIPEstat inference—
AS34927iFog-GmbH iFog GmbHUpstream (inferred)RIPEstat inference—
AS205112PHILUNET PHILUNET GmbHUpstream (inferred)RIPEstat inference—
AS394256CLOUDSINGULARITY - Tech Futures Interactive Inc.Upstream (inferred)RIPEstat inference—
AS401753BIXCE - BIXCE IncUpstream (inferred)RIPEstat inference—

Downstreams (inferred)

No downstream ASNs found for AS49933 in current data sources.

Combined from the evidence below: an ASN seen between AS49933 and the collectors (or inferred “left” by RIPEstat) is listed as upstream; one seen behind it (“right”) as downstream.

1. Observed path adjacencies (RouteViews)

ASNs that appear immediately next to AS49933 in AS paths seen by RouteViews collectors (prepends collapsed). These are path adjacencies, not confirmed BGP sessions, and the position says nothing certain about the commercial relationship.

ASNPosition in pathPathsCollectorsExample pathLast observed
AS29670
IN-BERLIN-AS Individual Network Berlin ("IN-Berlin") e.V.
Before (towards collector)17110
listamsix.ams, ix-br2.gru, route-views.linx, route-views.napafrica, route-views.sg, route-views.sydney, route-views3, route-views4, route-views5, route-views6
20912 6939 29670 49933

2. Direct sessions with RouteViews collectors

BGP sessions between AS49933 itself and a RouteViews collector (the AS feeds its routes to the collector).

AS49933 has no direct session with a RouteViews collector in the returned data.

3. Inferred neighbours (RIPEstat)

Neighbours inferred by RIPEstat from RIPE RIS AS paths. “Left” neighbours appear between AS49933 and the collector, “right” neighbours on the origin side. These are inferences, not confirmed relationships.

ASNSideInferencePowerIPv4 peersIPv6 peers
AS29670
IN-BERLIN-AS Individual Network Berlin ("IN-Berlin") e.V.
leftinferred upstream2520341
AS25091
IP-Max IP-Max SA
leftinferred upstream9013
AS34549
MEER-AS meerfarbig GmbH & Co. KG
leftinferred upstream506
AS8298
IPNG IPng Networks GmbH
leftinferred upstream303
AS34927
iFog-GmbH iFog GmbH
leftinferred upstream303
AS205112
PHILUNET PHILUNET GmbH
leftinferred upstream202
AS3214
XTOM xTom GmbH
uncertainuncertain101
AS34872
Servperso_Systems Sarah Rossius trading as Servperso Systems
uncertainuncertain101
AS60326
DEADBEEF-AS 0xDEADBEEF LTD
uncertainuncertain101
AS199854
ITBYPASSION Jens Thies
uncertainuncertain101
AS394256
CLOUDSINGULARITY - Tech Futures Interactive Inc.
leftinferred upstream101
AS401753
BIXCE - BIXCE Inc
leftinferred upstream101
AS403001
MIRAGE-GLOBAL-TECH - Mirage
uncertainuncertain101
  • Path adjacencies are derived from RouteViews AS paths for 1 of 1 prefixes originated by AS49933. Appearing next to AS49933 in a path does not by itself confirm a direct BGP session or its commercial relationship.
  • RIPEstat neighbours are inferred from RIS AS paths: 'left' neighbours appear between AS49933 and the collectors (likely upstreams), 'right' neighbours appear behind it.

Data sources for this page

SourceFreshnessResultFetchedProvider observationError
RouteViews APILiveOKNot reportedNone
RouteViews API (AS paths)LiveOKNone
RouteViews APILiveNo recordsNot reportedNone
RIPEstat Data APILiveOKNot reportedNone
RIPEstat Data API (AS names)CachedOKNot reportedNone

Page generated . See data sources and limitations.