Aller au contenu principal

Profil d’organisation

Organisation

FEELA-NET

FEELA-NET est suivi comme entreprise en CZ, avec des elements qui eclairent son identite, son role ou son contexte operationnel.

Dernière observation 2026-07-11

Preuves

16
Type d'information
FEELA-NET merite d'etre suivi car les changements de role, de relations, de position de gouvernance ou de perimetre operationnel peuvent affecter les operations reseau et la visibilite du marche.

Détails associés

  • Appuie l'identite, le role ou le contexte organisationnel de FEELA-NET.

  • RIPE documentation confirms that RIPE Database contents can be queried through RDAP and that autnum is a supported RDAP object type.

    official registry documentation

  • Mirrors RIPE WHOIS fields for AS212074, including as-name FEELA-NET, ORG-OF58-RIPE, org-name Ondrej Filip, country CZ, org-type LIR, maintainer MNT-FEELA, creation date, and import/export policy entries.

    third party registry mirror

  • Lists AS212074 as FEELA-NET in the Czech Republic and exposes traffic, protocol, security, and BGP announcement monitoring surfaces for the AS.

    internet measurement page

  • Lists AS212074 as FEELA-NET under Ondrej Filip, registry RIPE, allocation date , zero IPv4 and IPv6 routes, and a visible peers table including AS209431 and AS25192.

    asn lookup and whois mirror

  • States that RIPEstat's announced-prefixes endpoint returns all announced prefixes for a given ASN and describes query parameters and data output, supporting the recommended route-footprint refresh path.

    official documentation

  • Lists Ondrej Filip in the RIPE NCC member directory for the Czech Republic, supporting the resolved person/member context behind the registry material.

    official institutional directory

  • Shows the AS-number range 211356 to 212379, containing AS212074, assigned to RIPE NCC with RIPE WHOIS and RDAP endpoints.

    official number resource registry

  • States that the RIPEstat Data API is the public data interface for RIPEstat and lists endpoints including announced prefixes, AS overview, BGP state, RPKI validation, visibility, and whois.

    official measurement api documentation

  • IANA lists AS numbers as allocated to Regional Internet Registries and shows the block, which includes AS212074, as assigned by RIPE NCC with RIPE WHOIS and RDAP endpoints.

    Source publique

  • Explains RIPE NCC's RPKI service and BGP origin validation context, supporting route-security watchpoints for any originated AS212074 prefixes.

    official registry documentation

  • Displays RIPE-style WHOIS output for AS212074 with FEELA-NET, ORG-OF58-RIPE, Ondrej Filip organisation context, ASSIGNED status, MNT-FEELA, and role references, and states the query was served by RIPE Database Query Service version 1.121.

    whois mirror

  • Primary RIPE REST lookup path for the AS212074 aut-num object; use this endpoint to refresh the live registry object before publication.

    official registry api endpoint

  • RIPEstat documentation says the announced-prefixes endpoint returns all announced prefixes for a given ASN, with time-window parameters and prefix visibility timelines.

    official measurement api documentation

  • RDAP.org explains RDAP bootstrap behaviour and the general autnum lookup pattern, useful for understanding redirects to authoritative registry RDAP services.

  • Official RIPE RDAP endpoint for the current AS212074 autnum object; use as a primary registry refresh anchor before publication-level field claims.

    official registry endpoint

Dernière mise à jour: 2026-07-06