Network · data from 2026-11-12

AS36743 Ausra Systems AS36743

Registry name: AUSRA-SYSTEMS - Ausra LLC, US · PeeringDB

1IPv4 routes 0.0% RPKI valid · 100.0% with a route object

3IPv6 routes 100.0% RPKI valid · 100.0% with a route object

0RPKI invalid 0 origin · 0 maxLength

1No ROA 0 with no route object for this origin

0Low visibility seen by under 10% of full-table peers

0Route objects not announced registered with origin AS36743, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS36743, things to look at first. Visibility = full-table peers that see it, of 673 (IPv4) and 636 (IPv6) on 75 collectors. Also as routes.csv.


23.159.200.0/24	No ROA	RIR databaseARIN	673 100%	67
2a05:b0c7:1803::/48	Valid	RIR databaseRIPE	634 100%	69
2a05:b0c7:1820::/44	Valid	RIR databaseRIPE	634 100%	69
2a05:b0c7:19c0::/48	Valid	RIR databaseRIPE	634 100%	69

AS-SET

PeeringDB's irr_as_set for AS36743: AS-AUSRA. Expanded from the day's IRR dumps the way bgpq4 does against whois.radb.net: a name with a database is read from that database only, one without from the first database in RADB's order. "Not covered" = this network's own routes that a filter built from the set would leave out (AS36743 isn't in the set, or no route object for AS36743 covers the route; more-specifics of a route object are accepted down to /24 and /48, as with bgpq4 -A -R 24 / -R 48). Customers' routes aren't counted: the collectors show each route's origin, not which network it came through.

Name	Database	ASNs	Sets	Route objects	AS36743 in it	Not covered
AS-AUSRA	ARIN3 member sets in no database: AS-ATHARVA, AS150249:AS-ATHARVA, AS200566:AS-ATHARVA-INT	62	8	1,071	No	4

Name

Database

ASNs

Sets

Route objects

AS36743 in it

Not covered

AS-AUSRA

ARIN3 member sets in no database: AS-ATHARVA, AS150249:AS-ATHARVA, AS200566:AS-ATHARVA-INT

1,071

Fix list

The changes that would bring RPKI, the IRR and what's announced into line. Some are deliberate (a route object kept for a backup route, say); the network decides. All 5 are in fix.csv.

ROA: none1
AS-SET: own ASN1
AS-SET: missing member3

Change	Prefix or set	Detail	Full-table peers
ROA: none	23.159.200.0/24	No ROA covers it. Add a ROA for AS36743, maxLength 24.	673 of 673
AS-SET: own ASN	AS-AUSRA	AS36743 isn't in AS-AUSRA (ARIN) once expanded. Add AS36743 to it.
AS-SET: missing member	AS-AUSRA	AS-AUSRA (ARIN) lists AS-ATHARVA; no IRR database read has it.
AS-SET: missing member	AS-AUSRA	AS-AUSRA (ARIN) lists AS150249:AS-ATHARVA; no IRR database read has it.
AS-SET: missing member	AS-AUSRA	AS-AUSRA (ARIN) lists AS200566:AS-ATHARVA-INT; no IRR database read has it.

Change

Prefix or set

Detail

Full-table peers

ROA: none

23.159.200.0/24

No ROA covers it. Add a ROA for AS36743, maxLength 24.

673 of 673

AS-SET: own ASN

AS-AUSRA

AS36743 isn't in AS-AUSRA (ARIN) once expanded. Add AS36743 to it.

AS-SET: missing member

AS-AUSRA

AS-AUSRA (ARIN) lists AS-ATHARVA; no IRR database read has it.

AS-SET: missing member

AS-AUSRA

AS-AUSRA (ARIN) lists AS150249:AS-ATHARVA; no IRR database read has it.

AS-SET: missing member

AS-AUSRA

AS-AUSRA (ARIN) lists AS200566:AS-ATHARVA-INT; no IRR database read has it.

Route objects not announced

Every route object with origin AS36743 is announced.

Routes: the 08:00 UTC snapshots of 2026-11-12 from 75 RIPE RIS and RouteViews collectors. RPKI: our rpki-client run before the snapshot. IRR: the day's dumps of the five RIR databases and RADB's mirrors. The LEVEL3 and IDNIC databases publish no dump and aren't read, so route objects only there count as none.