bgpreport

Network · data from 2026-11-12

AS212071 SYDMAE

Registry name: SYDMAE Sydney Morrison, US · PeeringDB

6IPv4 routes 83.3% RPKI valid · 83.3% with a route object
2IPv6 routes 100.0% RPKI valid · 100.0% with a route object
1RPKI invalid 0 origin · 1 maxLength
0No ROA 1 with no route object for this origin
1Low visibility seen by under 10% of full-table peers
2Route objects not announced registered with origin AS212071, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS212071, 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.
140.235.62.0/24 Invalid: maxLength Nonecovered by 140.235.62.0/23 37 5%low visibility 19
140.235.60.0/24 Valid RIR databaseARIN 673 100% 67
23.147.40.0/24 Valid RIR databaseARIN 668 99% 67
130.12.94.0/24 Valid RIR databaseARIN 668 99% 67
140.235.61.0/24 Valid RIR databaseARIN 668 99% 67
140.235.62.0/23 Valid RIR databaseARIN 668 99% 67
2602:faa1::/40 Valid RIR databaseARIN 635 100% 67
2602:faa1:a4::/48 Valid RIR databaseARIN 635 100% 69

AS-SET

PeeringDB's irr_as_set for AS212071: AS212071:AS-ALL. 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 (AS212071 isn't in the set, or no route object for AS212071 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.

NameDatabaseASNsSets Route objectsAS212071 in itNot covered
AS212071:AS-ALL RIPE 3151 Yes 0

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 4 are in fix.csv.

  • ROA: maxLength1
  • Route object: none1
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
ROA: maxLength140.235.62.0/24ROA 140.235.62.0/23 AS212071 has maxLength 23; the route is a /24. Raise the maxLength, or add a ROA for 140.235.62.0/24.37 of 673
Route object: none140.235.62.0/24No route object for it. A route object for 140.235.62.0/23 with origin AS212071 covers it (filters allowing more-specifics accept it). Add a route object with origin AS212071 in the RIR database for the space.37 of 673

Route objects not announced

Route objects with origin AS212071 whose prefix no peer sees AS212071 announce. Many are kept on purpose (backup routes, space announced only in some places).

2602:f9bd:f03::/48ARINValid
2602:faa1:fe::/48ARINValid

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.