bgpreport

Network · data from 2026-11-12

AS60280 Республиканское унитарное предприятие «Национальный центр обмена трафиком»

Registry name: NTEC Republican Unitary Enterprise "National Traffic Exchange Center", BY · PeeringDB

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

Announced routes

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

195.50.23.0/24 No ROA RIR databaseRIPE 671 100% 68
195.50.24.0/24 No ROA RIR databaseRIPE 671 100% 68
2a02:e300::/48 Valid Nonecovered by 2a02:e300::/29 636 100% 68
2a02:e300:79::/48 Valid Nonecovered by 2a02:e300::/29 636 100% 68
185.11.79.0/24 Valid RIR databaseRIPE 673 100% 66
185.11.76.0/22 Valid RIR databaseRIPE 671 100% 68
185.11.76.0/24 Valid RIR databaseRIPE 671 100% 68
185.11.78.0/24 Valid RIR databaseRIPE 671 100% 68

AS-SET

PeeringDB's irr_as_set for AS60280: AS-NTEC. 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 (AS60280 isn't in the set, or no route object for AS60280 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 objectsAS60280 in itNot covered
AS-NTEC RIPElists itself further down4 member sets in no database: AS-AT, AS-CMFTKZ, AS-INITQ, AS207567:AS-INTEZIO 1,331167151,084 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 10 are in fix.csv.

  • ROA: none2
  • Route object: none2
  • AS-SET: missing member4
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
ROA: none195.50.23.0/24No ROA covers it. Add a ROA for AS60280, maxLength 24.671 of 673
ROA: none195.50.24.0/24No ROA covers it. Add a ROA for AS60280, maxLength 24.671 of 673
Route object: none2a02:e300::/48No route object for it. A route object for 2a02:e300::/29 with origin AS60280 covers it (filters allowing more-specifics accept it). Add a route object with origin AS60280 in the RIR database for the space.636 of 636
Route object: none2a02:e300:79::/48No route object for it. A route object for 2a02:e300::/29 with origin AS60280 covers it (filters allowing more-specifics accept it). Add a route object with origin AS60280 in the RIR database for the space.636 of 636
AS-SET: missing memberAS-NTECAS-NTEC (RIPE) lists AS-AT; no IRR database read has it.
AS-SET: missing memberAS-NTECAS-NTEC (RIPE) lists AS-CMFTKZ; no IRR database read has it.
AS-SET: missing memberAS-NTECAS-NTEC (RIPE) lists AS-INITQ; no IRR database read has it.
AS-SET: missing memberAS-NTECAS-NTEC (RIPE) lists AS207567:AS-INTEZIO; no IRR database read has it.

Route objects not announced

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

185.11.77.0/24RIPEInvalid: maxLength
2a02:e300::/29RIPENo ROA

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.