AS1930 Fundacao para a Ciencia e a Tecnologia, I.P.
AS1930 (RCCN) is registered to Fundacao para a Ciencia e a Tecnologia, I.P. in PT, through RIPE. It originates 79 prefixes in the global routing table.
Who holds AS1930
Names from RIPE NCC’s daily list of every allocated AS number. The ASN lookup fetches the full WHOIS record live.
WHOIS recordRIPE
% This is the RIPE Database query service. % The objects are in RPSL format. % % The RIPE Database is subject to Terms and Conditions. % See https://docs.db.ripe.net/terms-conditions.html % Note: this output has been filtered. % To receive output for a database update, use the "-B" flag. % Information related to 'AS1930 - AS1930' as-block: AS1930 - AS1930 descr: RIPE NCC ASN block remarks: These AS Numbers are assigned to network operators in the RIPE NCC service region. mnt-by: RIPE-NCC-HM-MNT created: 2018-11-22T15:27:14Z last-modified: 2018-11-22T15:27:14Z source: RIPE % Information related to 'AS1930' % Abuse contact for 'AS1930' is 'report@csirt.fct.pt' aut-num: AS1930 as-name: RCCN descr: -------------------------------------------------------- descr: Fundacao para a Ciencia e a Tecnologia, I.P. descr: -------------------------------------------------------- descr: Rede Ciencia Tecnologia e Sociedade (RCTS) descr: Former "Rede da Comunidade Cientifica Nacional" (RCCN) descr: Portuguese Research & Education Network descr: Portugal, Europe org: ORG-FpaC1-RIPE remarks: -------------------------------------------------------- remarks: URL: http://www.fccn.pt remarks: FCCN - Foundation for National Scientific Computing remarks: FCCN manages the: remarks: * Portuguese R&E Network - RCTS; remarks: * Portuguese Internet Exchange (GigaPix); remarks: FCCN is a FCT,I.P. Unit, as of 2013-10-01 remarks: -------------------------------------------------------- remarks: We have an Open Peering Policy remarks: We peer over IPv4 & IPv6 remarks: Contact: noc@fccn.pt remarks: -------------------------------------------------------- remarks: TRANSIT PROVIDERS remarks: -------------------------------------------------------- remarks: # GEANT import: from AS20965 action pref=100; accept ANY mp-import: afi ipv6.unicast from AS20965 action pref=100; accept ANY mp-import: afi ipv4.multicast from AS20965 action pref=100; accept ANY mp-import: afi ipv6.multicast from AS20965 action pref=100; accept ANY export: to AS20965 announce AS-RCCN mp-export: afi ipv6.unicast to AS20965 announce AS-RCCN mp-export: afi ipv4.multicast to AS20965 announce AS-RCCN mp-export: afi ipv6.multicast to AS20965 announce AS-RCCN remarks: # GEANT IAS import: from AS21320 action pref=100; accept ANY mp-import: afi ipv6.unicast from AS21320 action pref=100; accept ANY mp-import: afi ipv4.multicast from AS21320 action pref=100; accept ANY mp-import: afi ipv6.multicast from AS21320 action pref=100; accept ANY export: to AS21320 announce AS-RCCN mp-export: afi ipv6.unicast to AS21320 announce AS-RCCN mp-export: afi ipv4.multicast to AS21320 announce AS-RCCN mp-export: afi ipv6.multicast to AS21320 announce AS-RCCN remarks: # COGENT import: from AS174 action pref=100; accept ANY mp-import: afi ipv6.unicast from AS174 action pref=100; accept ANY export: to AS174 announce AS-RCCN mp-export: afi ipv6.unicast to AS174 announce AS-RCCN remarks: -------------------------------------------------------- remarks: MEMBERS remarks: -------------------------------------------------------- remarks: # INESC import: from AS5516 action pref=100; accept AS5516 export: to AS5516 announce ANY remarks: # GIGAPIX import: from AS12833 action pref=100; accept AS12833 export: to AS12833 announce ANY remarks: # INESCTEC import: from AS35038 action pref=100; accept AS35038 export: to AS35038 announce ANY remarks: # EMSA import: from AS57350 action pref=100; accept AS57350 export: to AS57350 announce ANY remarks: # RAE import: from AS199155 action pref=100; accept AS199155 export: to AS19
What AS1930 announces
Prefixes originated by AS1930 in the routing table our collectors hold (kept current as routes change), each checked against the RPKI (every ten minutes) and the IRR (daily).
Announced prefixes
Each opens its own page: who announces it, the paths our collectors see, its ROAs and route objects.
RPKI valid RPKI invalid no ROA covers it
Who AS1930 buys transit from
Inferred from the AS paths in the RouteViews tables and our own collectors’ feeds, refreshed every 4 hours, most-seen first. 4 upstreams.
Who buys transit from AS1930
8 downstreams, its customers; those marked ASPA name AS1930 as a provider in theirs.
Provider authorization
AS1930 publishes no ASPA of its own. 1 AS name it as a provider in theirs. Check a path.
The 1 ASes that name AS1930 as a provider
Routing registry objects
From the mirrored IRR databases (RADB, the five RIRs and more). Look it up live.
| Source | as-name | Maintained by |
|---|---|---|
| RIPE | RCCN | RIPE-NCC-LEGACY-MNT, AS1930-MNT |
Route objects with origin AS1930: RIPE 88