bgpreport

Network · data from 2026-11-12

AS269615 FIBRAXX TELECOM

Registry name: AS269615 - DELTA TELECOM, BR · PeeringDB

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

Announced routes

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

2804:673c:600::/41 No ROA Nonecovered by 2804:673c::/34 634 100% 67
2804:673c:610::/46 No ROA Nonecovered by 2804:673c::/34 634 100% 67
2804:673c:618::/45 No ROA Nonecovered by 2804:673c::/34 634 100% 67
2804:673c:8000::/40 No ROA Nonecovered by 2804:673c:8000::/33 634 100% 67
2804:673c:beba::/48 No ROA Nonecovered by 2804:673c:8000::/33 634 100% 67
2804:673c:c300::/40 No ROA Nonecovered by 2804:673c:8000::/33 634 100% 67
2804:673c:c400::/40 No ROA Nonecovered by 2804:673c:8000::/33 634 100% 67
2804:673c:680::/41 No ROA Nonecovered by 2804:673c::/34 1 0%low visibility 1
2804:673c:8000::/34 No ROA Nonecovered by 2804:673c:8000::/33 1 0%low visibility 1
2804:673c:c200::/40 No ROA Nonecovered by 2804:673c:8000::/33 1 0%low visibility 1
45.189.222.0/24 No ROA Other IRR onlyTC 667 99% 67
2804:673c::/32 No ROA Other IRR onlyALTDB, RADB, TC 7 1%low visibility 4
45.189.221.0/24 No ROA Other IRR onlyTC 4 1%low visibility 4
45.189.223.0/24 No ROA Other IRR onlyTC 4 1%low visibility 4
45.189.220.0/24 No ROA Other IRR onlyTC 3 0%low visibility 3

AS-SET

PeeringDB's irr_as_set for AS269615: AS-FIBRAXXTELECOM. 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 (AS269615 isn't in the set, or no route object for AS269615 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 objectsAS269615 in itNot covered
AS-FIBRAXXTELECOM ALTDB 1111 Yes 0
TC (also) 1111 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 36 are in fix.csv.

  • ROA: none15
  • Route object: none10
  • Route object: RIR5
  • Route object: not announced6
ChangePrefix or setDetailFull-table peers
ROA: none2804:673c:600::/41No ROA covers it. Add a ROA for AS269615, maxLength 41.634 of 636
Route object: none2804:673c:600::/41No route object for it. A route object for 2804:673c::/34 with origin AS269615 covers it (filters allowing more-specifics accept it). Add a route object with origin AS269615 in the RIR database for the space.634 of 636
ROA: none2804:673c:610::/46No ROA covers it. Add a ROA for AS269615, maxLength 46.634 of 636
Route object: none2804:673c:610::/46No route object for it. A route object for 2804:673c::/34 with origin AS269615 covers it (filters allowing more-specifics accept it). Add a route object with origin AS269615 in the RIR database for the space.634 of 636
ROA: none2804:673c:618::/45No ROA covers it. Add a ROA for AS269615, maxLength 45.634 of 636
Route object: none2804:673c:618::/45No route object for it. A route object for 2804:673c::/34 with origin AS269615 covers it (filters allowing more-specifics accept it). Add a route object with origin AS269615 in the RIR database for the space.634 of 636
ROA: none2804:673c:8000::/40No ROA covers it. Add a ROA for AS269615, maxLength 40.634 of 636
Route object: none2804:673c:8000::/40No route object for it. A route object for 2804:673c:8000::/33 with origin AS269615 covers it (filters allowing more-specifics accept it). Add a route object with origin AS269615 in the RIR database for the space.634 of 636
ROA: none2804:673c:beba::/48No ROA covers it. Add a ROA for AS269615, maxLength 48.634 of 636
Route object: none2804:673c:beba::/48No route object for it. A route object for 2804:673c:8000::/33 with origin AS269615 covers it (filters allowing more-specifics accept it). Add a route object with origin AS269615 in the RIR database for the space.634 of 636
ROA: none2804:673c:c300::/40No ROA covers it. Add a ROA for AS269615, maxLength 40.634 of 636
Route object: none2804:673c:c300::/40No route object for it. A route object for 2804:673c:8000::/33 with origin AS269615 covers it (filters allowing more-specifics accept it). Add a route object with origin AS269615 in the RIR database for the space.634 of 636
ROA: none2804:673c:c400::/40No ROA covers it. Add a ROA for AS269615, maxLength 40.634 of 636
Route object: none2804:673c:c400::/40No route object for it. A route object for 2804:673c:8000::/33 with origin AS269615 covers it (filters allowing more-specifics accept it). Add a route object with origin AS269615 in the RIR database for the space.634 of 636
ROA: none2804:673c:680::/41No ROA covers it. Add a ROA for AS269615, maxLength 41.1 of 636
Route object: none2804:673c:680::/41No route object for it. A route object for 2804:673c::/34 with origin AS269615 covers it (filters allowing more-specifics accept it). Add a route object with origin AS269615 in the RIR database for the space.1 of 636
ROA: none2804:673c:8000::/34No ROA covers it. Add a ROA for AS269615, maxLength 34.1 of 636
Route object: none2804:673c:8000::/34No route object for it. A route object for 2804:673c:8000::/33 with origin AS269615 covers it (filters allowing more-specifics accept it). Add a route object with origin AS269615 in the RIR database for the space.1 of 636
ROA: none2804:673c:c200::/40No ROA covers it. Add a ROA for AS269615, maxLength 40.1 of 636
Route object: none2804:673c:c200::/40No route object for it. A route object for 2804:673c:8000::/33 with origin AS269615 covers it (filters allowing more-specifics accept it). Add a route object with origin AS269615 in the RIR database for the space.1 of 636
ROA: none45.189.222.0/24No ROA covers it. Add a ROA for AS269615, maxLength 24.667 of 673
Route object: RIR45.189.222.0/24Route object only in TC. Add it in the RIR database for the space.667 of 673
ROA: none2804:673c::/32No ROA covers it. Add a ROA for AS269615, maxLength 32.7 of 636
Route object: RIR2804:673c::/32Route object only in ALTDB, RADB, TC. Add it in the RIR database for the space.7 of 636
ROA: none45.189.221.0/24No ROA covers it. Add a ROA for AS269615, maxLength 24.4 of 673
Route object: RIR45.189.221.0/24Route object only in TC. Add it in the RIR database for the space.4 of 673
ROA: none45.189.223.0/24No ROA covers it. Add a ROA for AS269615, maxLength 24.4 of 673
Route object: RIR45.189.223.0/24Route object only in TC. Add it in the RIR database for the space.4 of 673
ROA: none45.189.220.0/24No ROA covers it. Add a ROA for AS269615, maxLength 24.3 of 673
Route object: RIR45.189.220.0/24Route object only in TC. Add it in the RIR database for the space.3 of 673

Route objects not announced

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

45.189.220.0/22ALTDB, RADB, TCNo ROA
45.189.220.0/23TCNo ROA
45.189.222.0/23TCNo ROA
2804:673c::/34ALTDBNo ROA
2804:673c:4000::/34ALTDBNo ROA
2804:673c:8000::/33ALTDBNo 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.