bgpreport

Network · data from 2026-11-12

AS56876 Ociris GmbH

Registry name: GPORTAL Ociris GmbH, DE · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS56876, 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.

81.31.252.0/22 Valid RIR databaseRADB, RIPE 673 100% 67
83.147.212.0/22 Valid RIR databaseRADB, RIPE 673 100% 67
83.223.192.0/20 Valid RIR databaseRIPE 673 100% 67
83.223.202.0/24 Valid RIR databaseRADB, RIPE 673 100% 67
85.202.82.0/24 Valid RIR databaseRIPE 673 100% 67
88.216.216.0/22 Valid RIR databaseRADB, RIPE 673 100% 67
94.250.192.0/19 Valid RIR databaseRADB, RIPE 673 100% 67
94.250.214.0/24 Valid RIR databaseRADB, RIPE 673 100% 67
94.250.218.0/24 Valid RIR databaseRADB, RIPE 673 100% 67
155.133.0.0/24 Valid RIR databaseRIPE 673 100% 67
176.57.128.0/18 Valid RIR databaseRADB, RIPE 673 100% 67
176.57.134.0/24 Valid RIR databaseRIPE 673 100% 67
176.57.186.0/24 Valid RIR databaseRADB, RIPE 673 100% 67
176.57.190.0/24 Valid RIR databaseRADB, RIPE 673 100% 67
185.137.120.0/22 Valid RIR databaseRADB, RIPE 673 100% 67
185.185.81.0/24 Valid RIR databaseRIPE 673 100% 67
185.208.204.0/23 Valid RIR databaseRIPE 673 100% 67
185.249.226.0/24 Valid RIR databaseRIPE 673 100% 67
193.22.154.0/23 Valid RIR databaseRIPE 673 100% 67
193.43.71.0/24 Valid RIR databaseRIPE 673 100% 67
193.192.58.0/24 Valid RIR databaseRADB, RIPE 673 100% 67
193.192.59.0/24 Valid RIR databaseRADB, RIPE 673 100% 67
194.113.65.0/24 Valid RIR databaseRIPE 673 100% 67
194.233.0.0/22 Valid RIR databaseRADB, RIPE 673 100% 67
45.130.107.0/24 Valid RIR databaseRIPE 672 100% 67
45.137.246.0/24 Valid RIR databaseRADB, RIPE 672 100% 67
83.223.201.0/24 Valid RIR databaseRADB, RIPE 672 100% 67
83.223.207.0/24 Valid RIR databaseRADB, RIPE 672 100% 67
94.250.196.0/24 Valid RIR databaseRADB, RIPE 672 100% 67
94.250.200.0/24 Valid RIR databaseRADB, RIPE 672 100% 67
94.250.215.0/24 Valid RIR databaseRADB, RIPE 672 100% 67
94.250.222.0/24 Valid RIR databaseRIPE 672 100% 67
176.57.143.0/24 Valid RIR databaseRADB, RIPE 672 100% 67
45.137.244.0/24 Valid RIR databaseRIPE 671 100% 67
45.137.247.0/24 Valid RIR databaseRIPE 671 100% 67
94.250.221.0/24 Valid RIR databaseRADB, RIPE 671 100% 67
176.57.135.0/24 Valid RIR databaseRADB, RIPE 671 100% 67
83.223.197.0/24 Valid RIR databaseRADB, RIPE 667 99% 67
83.223.199.0/24 Valid RIR databaseRADB, RIPE 667 99% 67
83.223.200.0/24 Valid RIR databaseRIPE 3 0%low visibility 3
83.223.203.0/24 Valid RIR databaseRIPE 3 0%low visibility 3
83.223.204.0/24 Valid RIR databaseRIPE 3 0%low visibility 3
83.223.206.0/24 Valid RIR databaseRIPE 3 0%low visibility 3

AS-SET

PeeringDB's irr_as_set for AS56876: AS-GPORTAL. 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 (AS56876 isn't in the set, or no route object for AS56876 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 objectsAS56876 in itNot covered
AS-GPORTAL RADB 21147 Yes 0
RIPE (also)lists itself further down30 member sets in no database: AS-17290:AS-AUSTIN-HADLEY, AS-AS21868, AS-HELIACAL, AS-HOSTINGFUZE, AS-NIXCON … 1,19725336,901 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 13 are in fix.csv.

  • Route object: not announced13

Route objects not announced

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

45.137.245.0/24RIPEInvalid: origin
45.137.246.0/23RIPENo ROA
83.223.205.0/24RIPEValid
94.250.204.0/24RADB, RIPEValid
94.250.212.0/24RIPEValid
94.250.213.0/24RIPEValid
94.250.216.0/24RADB, RIPEValid
94.250.219.0/24RIPEValid
176.57.130.0/24RADB, RIPEValid
176.57.158.0/24RIPEValid
193.192.58.0/23RADB, RIPEValid
2a00:e440::/32RADB, RIPEValid
2a0f:5707:aab1::/48RIPEValid

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.