bgpreport

Network · data from 2026-11-12

AS203522 FCSE / IXP.mk Upstream Services

Registry name: NOGMK Faculty of Computer Science and Engineering - Ss. Cyril and Methodius University in Skopje, MK · PeeringDB

1IPv4 routes 0.0% RPKI valid · 100.0% with a route object
1IPv6 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 AS203522, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS203522, 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.
194.149.139.0/24 No ROA RIR databaseRIPE 672 100% 67
2001:67c:a60::/48 Valid RIR databaseRIPE 632 99% 69

AS-SET

PeeringDB's irr_as_set for AS203522: RIPE::AS203522:AS-NOGMK-TRANSIT. 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 (AS203522 isn't in the set, or no route object for AS203522 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 objectsAS203522 in itNot covered
RIPE::AS203522:AS-NOGMK-TRANSIT RIPE 2256,228 No 2

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

  • ROA: none1
  • AS-SET: own ASN1
ChangePrefix or setDetailFull-table peers
ROA: none194.149.139.0/24No ROA covers it. Add a ROA for AS203522, maxLength 24.672 of 673
AS-SET: own ASNRIPE::AS203522:AS-NOGMK-TRANSITAS203522 isn't in AS203522:AS-NOGMK-TRANSIT (RIPE) once expanded. Add AS203522 to it.

Route objects not announced

Every route object with origin AS203522 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.