ResearchRouting table, RPKI, IRR & looking glass

AS204319 Trigion Alarmcentrale BV

AS204319 (TRIGION) is registered to Trigion Alarmcentrale BV in NL. It originates 5 prefixes in the global routing table.

4
IPv4 prefixes
1
IPv6 prefixes
1,024
IPv4 addresses
100%
RPKI valid

Who holds AS204319

Names from RIPE NCC’s daily list of every allocated AS number. The ASN lookup fetches the full WHOIS record live.

AS number
AS204319
Handle
TRIGION
Organization
Trigion Alarmcentrale BV
Country
NL
ASPA
None published

What AS204319 announces

Prefixes originated by AS204319 in the RouteViews table (refreshed every four hours), each checked against the RPKI (every ten minutes) and the IRR (daily).

IPv4 prefixes
4
IPv6 prefixes
1
IPv4 addresses
1,024 (4 /24s)
RPKI valid
5 100%
RPKI invalid
0
RPKI not found
0
ROAs naming AS204319
2
With an IRR route object
5 100%

Announced prefixes

Each opens its own page: who announces it, the paths our collectors see, its ROAs and route objects.

IPv4 (4)
IPv6 (1)

RPKI valid   RPKI invalid   no ROA covers it

Who AS204319 is reached through

The AS just before AS204319 in the paths our looking glass collectors hold, for 5 of its prefixes. Usually a transit provider, sometimes a peer. The number is how many of those prefixes it was seen on.

Routing registry objects

From the mirrored IRR databases (RADB, the five RIRs and more). Look it up live.

Sourceas-nameMaintained by
RIPETRIGIONRIPE-NCC-END-MNT, NL-TRIGION-1-MNT

Route objects with origin AS204319: RIPE 5

as-sets that list AS204319 (1)